Merge pull request #387 from metabase/docs-time-grouping-params->master

[auto-build] docs-time-grouping-params -> master

Author: jeff-bruemmer

_docs/master/api.html

@@ -128,20 +128,27 @@ config:
     ee-openai-api-key: null
     ee-openai-model: gpt-4-turbo-preview
     email-from-address: [email protected]
+    email-from-address-override: [email protected]
     email-from-name: null
     email-max-recipients-per-second: null
     email-reply-to: null
     email-smtp-host: null
+    email-smtp-host-override: null
     email-smtp-password: null
+    email-smtp-password-override: null
     email-smtp-port: null
+    email-smtp-port-override: null
     email-smtp-security: none
+    email-smtp-security-override: ssl
     email-smtp-username: null
+    email-smtp-username-override: null
     embedding-app-origins-interactive: null
     embedding-app-origins-sdk: localhost:*
     embedding-homepage: hidden
     embedding-secret-key: null
     enable-embedding-interactive: false
     enable-embedding-sdk: false
+    enable-embedding-simple: false
     enable-embedding-static: false
     enable-password-login: true
     enable-pivoted-exports: true
@@ -257,6 +264,7 @@ config:
     site-url: null
     slack-app-token: null
     slack-bug-report-channel: metabase-bugs
+    smtp-override-enabled: false
     source-address-header: X-Forwarded-For
     sql-jdbc-fetch-size: 500
     ssh-heartbeat-interval-sec: 180

_docs/master/configuring-metabase/config-template.md

@@ -437,6 +437,16 @@ This feature is experimental.
 
 The email address you want to use for the sender of emails.
 
+### `MB_EMAIL_FROM_ADDRESS_OVERRIDE`
+
+> Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.
+
+- Type: string
+- Default: `[email protected]`
+- [Configuration file name](./config-file): `email-from-address-override`
+
+The email address you want to use for the sender of emails from your custom SMTP server.
+
 ### `MB_EMAIL_FROM_NAME`
 
 - Type: string
@@ -471,6 +481,16 @@ The email address you want the replies to go to, if different from the from addr
 
 The address of the SMTP server that handles your emails.
 
+### `MB_EMAIL_SMTP_HOST_OVERRIDE`
+
+> Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.
+
+- Type: string
+- Default: `null`
+- [Configuration file name](./config-file): `email-smtp-host-override`
+
+The address of the custom SMTP server that handles your emails.
+
 ### `MB_EMAIL_SMTP_PASSWORD`
 
 - Type: string
@@ -479,6 +499,16 @@ The address of the SMTP server that handles your emails.
 
 SMTP password.
 
+### `MB_EMAIL_SMTP_PASSWORD_OVERRIDE`
+
+> Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.
+
+- Type: string
+- Default: `null`
+- [Configuration file name](./config-file): `email-smtp-password-override`
+
+Custom SMTP server password.
+
 ### `MB_EMAIL_SMTP_PORT`
 
 - Type: integer
@@ -487,6 +517,16 @@ SMTP password.
 
 The port your SMTP server uses for outgoing emails.
 
+### `MB_EMAIL_SMTP_PORT_OVERRIDE`
+
+> Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.
+
+- Type: integer
+- Default: `null`
+- [Configuration file name](./config-file): `email-smtp-port-override`
+
+The port your custom SMTP server uses for outgoing emails. Only ports 465, 587, and 2525 are supported.
+
 ### `MB_EMAIL_SMTP_SECURITY`
 
 - Type: keyword
@@ -495,6 +535,16 @@ The port your SMTP server uses for outgoing emails.
 
 SMTP secure connection protocol. (tls, ssl, starttls, or none).
 
+### `MB_EMAIL_SMTP_SECURITY_OVERRIDE`
+
+> Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.
+
+- Type: keyword
+- Default: `:ssl`
+- [Configuration file name](./config-file): `email-smtp-security-override`
+
+SMTP secure connection protocol for your custom server. (tls, ssl, or starttls).
+
 ### `MB_EMAIL_SMTP_USERNAME`
 
 - Type: string
@@ -503,6 +553,16 @@ SMTP secure connection protocol. (tls, ssl, starttls, or none).
 
 SMTP username.
 
+### `MB_EMAIL_SMTP_USERNAME_OVERRIDE`
+
+> Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.
+
+- Type: string
+- Default: `null`
+- [Configuration file name](./config-file): `email-smtp-username-override`
+
+Custom SMTP server username.
+
 ### `MB_EMBEDDING_APP_ORIGIN [DEPRECATED]`
 
 > Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.
@@ -579,6 +639,14 @@ Allow admins to embed Metabase via interactive embedding?
 
 Allow admins to embed Metabase via the SDK?
 
+### `MB_ENABLE_EMBEDDING_SIMPLE`
+
+- Type: boolean
+- Default: `false`
+- [Configuration file name](./config-file): `enable-embedding-simple`
+
+Allow admins to embed Metabase via Embedded Analytics JS?
+
 ### `MB_ENABLE_EMBEDDING_STATIC`
 
 - Type: boolean
@@ -1650,6 +1718,16 @@ The name of the channel where bug reports should be posted.
 
 The name of the channel to which Metabase files should be initially uploaded.
 
+### `MB_SMTP_OVERRIDE_ENABLED`
+
+> Only available on Metabase [Pro](/product/pro) and [Enterprise](/product/enterprise) plans.
+
+- Type: boolean
+- Default: `false`
+- [Configuration file name](./config-file): `smtp-override-enabled`
+
+Whether to use the custom SMTP server rather than the standard settings.
+
 ### `MB_SOURCE_ADDRESS_HEADER`
 
 - Type: string

_docs/master/configuring-metabase/environment-variables.md

@@ -140,7 +140,7 @@ LIMIT 0
 
 By default, this query runs against your database during setup and again every hour. This scanning query is fast with most relational databases but can be slower with MongoDB and some [community-built database drivers](../developers-guide/community-drivers). Syncing can't be turned off completely, otherwise Metabase wouldn't work.
 
-Here's the kind of data that syncs get and why:
+Here's the kind of data that gets synced and why:
 
 | What             | Why                                          |
 | ---------------- | -------------------------------------------- |

_docs/master/databases/sync-scan.md

@@ -34,6 +34,13 @@ layout: new-docs
 
 - Added a feature `:expressions/today` for drivers that support generating a date for the current day.
 
+- Added the driver multi-method `driver/set-database-used!` for drivers to set a database on the connection with statements like `USE DATABASE`.
+
+## Metabase 0.55.9
+
+- Add multi-method `driver/do-with-resilient-connection` for executing functions in a context where closed connections may be automatically reopened
+
+
 ## Metabase 0.55.0
 
 - Add the multi-method `->date` that allows the driver to control how to cast strings and temporal types to dates.

_docs/master/developers-guide/driver-changelog.md

@@ -223,15 +223,17 @@ Prior to running Cypress against Metabase® Enterprise Edition™, set `MB_EDITI
 
 **Enterprise instance will start without a premium token!**
 
-If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests. We achieve this by prefixing environment variables with `CYPRESS_`.
-You should provide two tokens that correspond to the `EE/PRO` self-hosted (all features enabled) and `STARTER` Cloud (no features enabled) Metabase plans. For more information, please see [Metabase pricing page](/pricing/). (note: only a few tests require the no features token)
+If you want to test premium features (feature flags), valid tokens need to be available to all Cypress tests.
+You should provide 4 tokens:
 
-- `CYPRESS_ALL_FEATURES_TOKEN`
-- `CYPRESS_NO_FEATURES_TOKEN`
+- MB_ALL_FEATURES_TOKEN: all feature enabled, including new feature not released yet to customers
+- MB_STARTER_CLOUD_TOKEN: only 'hosting' feature enabled to simulate the starter plan on cloud
+- MB_PRO_CLOUD_TOKEN: PRO features enabled + 'hosting' to simulate the pro plan on cloud
+- MB_PRO_SELF_HOSTED_TOKEN: PRO features but no 'hosting' to simulate the pro self-hosted plan
 
-```
-MB_EDITION=ee ENTERPRISE_TOKEN=xxxxxx yarn test-cypress
-```
+You can configure these via ENVs or via the `cypress.env.json` file (see `cypress.env.json.example` for an example).
+
+For more information, please see [Metabase pricing page](/pricing/).
 
 If you navigate to the `/admin/settings/license` page, the license input field should display the active token. Be careful when sharing screenshots!