diff --git a/docs/access-management/sso.md b/docs/access-management/sso.md index b9b8574ea29..5f775c3c192 100644 --- a/docs/access-management/sso.md +++ b/docs/access-management/sso.md @@ -31,7 +31,7 @@ import DocCardList from '@theme/DocCardList'; *Note:* you were already logged into your company’s Okta account you might not see any login screen and directly get forwarded back to Airbyte Cloud. - + Accessing your self hosted Airbyte will automatically forward you to your IdP's login page (e.g. Okta login page). Log into your work account and you’ll be forwarded back to your Airbyte and be logged in. diff --git a/docs/cloud/managing-airbyte-cloud/review-sync-history.md b/docs/cloud/managing-airbyte-cloud/review-sync-history.md index a161887f521..fec71022176 100644 --- a/docs/cloud/managing-airbyte-cloud/review-sync-history.md +++ b/docs/cloud/managing-airbyte-cloud/review-sync-history.md @@ -8,7 +8,7 @@ The job history displays information about synced data, such as the amount of da ![Job History](./assets/connection-job-history.png) -To review the sync history, click a connection in the list to view its sync history. Sync History displays the sync status or [clear](/operator-guides/clear) status. The sync status is defined as: +To review the sync history, click a connection in the list and navigate to the "Job History" tab to view its sync history. The page displays recent syncs and their statuses. The sync status is defined as: | Status | Description | | ------------------- | ----------------------------------------------------------------- | @@ -18,6 +18,8 @@ To review the sync history, click a connection in the list to view its sync hist | Cancelled | The sync was cancelled manually before finishing | | Running | The sync is currently running | +If you have recently run a [refresh](/operator-guides/refreshes) or [clear](/operator-guides/clear), you will also see this noted on the Job History page and their corresponding status. + ## Sync summary Each sync shows the time the sync was initiated and additional metadata. This information can help in understanding sync performance over time. @@ -29,11 +31,9 @@ Each sync shows the time the sync was initiated and additional metadata. This in | x loaded records | Number of records the destination confirmed it received. | | xh xm xs | Total time (hours, minutes, seconds) for the sync to complete | -:::note +While most syncs only contain a single attempt, a sync can sometimes fail. In the event of a failure, Airbyte will make several attempts to sync your data before waiting for the next sync to retry. You can read more about our retry approach [here](../../understanding-airbyte/jobs.md#retry-rules). -In the event of a failure, Airbyte will make several attempts to sync your data before waiting for the next sync to retry. The latest rules can be read about [here](../../understanding-airbyte/jobs.md#retry-rules). - -::: +Airbyte summarizes metrics in the sync summary across all the attempts in the sync. As a result, you may observe that the number of records extracted is higher than the number of records loaded if an attempt fails during the extraction process. A successful sync status means that all the records from the source have been successfully written to the destination. :::info diff --git a/docs/deploying-airbyte/deploying-airbyte.md b/docs/deploying-airbyte/deploying-airbyte.md index 4d09aaa0e57..bfa03e760c9 100644 --- a/docs/deploying-airbyte/deploying-airbyte.md +++ b/docs/deploying-airbyte/deploying-airbyte.md @@ -1,3 +1,6 @@ +--- +products: oss-community, oss-enterprise +--- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/docs/deploying-airbyte/infrastructure/aws.md b/docs/deploying-airbyte/infrastructure/aws.md index d5090d6cd4f..e37d370a1e9 100644 --- a/docs/deploying-airbyte/infrastructure/aws.md +++ b/docs/deploying-airbyte/infrastructure/aws.md @@ -1,3 +1,7 @@ +--- +products: oss-community, oss-enterprise +--- + # Amazon Web Services (AWS) Airbyte supports Amazon Web Services as a Cloud Provider. There are several ways that you can deploy Airbyte using AWS. diff --git a/docs/deploying-airbyte/infrastructure/azure.md b/docs/deploying-airbyte/infrastructure/azure.md index e139ffc718c..186ebbd8613 100644 --- a/docs/deploying-airbyte/infrastructure/azure.md +++ b/docs/deploying-airbyte/infrastructure/azure.md @@ -1 +1,5 @@ +--- +products: oss-community, oss-enterprise +--- + # Microsoft Azure \ No newline at end of file diff --git a/docs/deploying-airbyte/infrastructure/gcp.md b/docs/deploying-airbyte/infrastructure/gcp.md index c0e1dc17660..7921ca98bbe 100644 --- a/docs/deploying-airbyte/infrastructure/gcp.md +++ b/docs/deploying-airbyte/infrastructure/gcp.md @@ -1 +1,5 @@ +--- +products: oss-community, oss-enterprise +--- + # Google Cloud Platform (GCP) \ No newline at end of file diff --git a/docs/deploying-airbyte/integrations/database.md b/docs/deploying-airbyte/integrations/database.md index 33e5d20d5e4..0ecf19cdfc8 100644 --- a/docs/deploying-airbyte/integrations/database.md +++ b/docs/deploying-airbyte/integrations/database.md @@ -1,3 +1,7 @@ +--- +products: oss-community, oss-enterprise +--- + # External Database For production deployments, we recommend using a dedicated database instance for better reliability, and backups (such as AWS RDS or GCP Cloud SQL) instead of the default internal Postgres database (`airbyte/db`) that Airbyte spins up within the Kubernetes cluster. diff --git a/docs/deploying-airbyte/integrations/ingress.md b/docs/deploying-airbyte/integrations/ingress.md index 2696f2ff6cb..1df6f18f45c 100644 --- a/docs/deploying-airbyte/integrations/ingress.md +++ b/docs/deploying-airbyte/integrations/ingress.md @@ -1,4 +1,6 @@ - +--- +products: oss-community, oss-enterprise +--- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/docs/deploying-airbyte/integrations/monitoring.md b/docs/deploying-airbyte/integrations/monitoring.md index 2ddbe89cb91..3bff399695f 100644 --- a/docs/deploying-airbyte/integrations/monitoring.md +++ b/docs/deploying-airbyte/integrations/monitoring.md @@ -1 +1,5 @@ +--- +products: oss-community, oss-enterprise +--- + # Monitoring \ No newline at end of file diff --git a/docs/deploying-airbyte/integrations/secrets.md b/docs/deploying-airbyte/integrations/secrets.md index 1f9a6482742..5d2255ab957 100644 --- a/docs/deploying-airbyte/integrations/secrets.md +++ b/docs/deploying-airbyte/integrations/secrets.md @@ -1,3 +1,6 @@ +--- +products: oss-community, oss-enterprise +--- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/docs/deploying-airbyte/integrations/storage.md b/docs/deploying-airbyte/integrations/storage.md index e3f0a929624..f8c55825434 100644 --- a/docs/deploying-airbyte/integrations/storage.md +++ b/docs/deploying-airbyte/integrations/storage.md @@ -1,3 +1,6 @@ +--- +products: oss-community, oss-enterprise +--- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/docs/integrations/sources/snapchat-marketing.md b/docs/integrations/sources/snapchat-marketing.md index de86042141c..f08c747c333 100644 --- a/docs/integrations/sources/snapchat-marketing.md +++ b/docs/integrations/sources/snapchat-marketing.md @@ -1,6 +1,6 @@ # Snapchat Marketing -This page guides you through the process of setting up the Snapchat Marketing source connector. +This page guides you through the process of setting up the [Snapchat Marketing](https://marketingapi.snapchat.com/docs/) source connector. ## Prerequisites @@ -8,28 +8,24 @@ This page guides you through the process of setting up the Snapchat Marketing so **For Airbyte Cloud:** -- A Snapchat Marketing account with permission to access data from accounts you want to sync +- An existing Snapchat Marketing business account **For Airbyte Open Source:** -- client_id -- client_secret -- refresh_token -- start_date -- end_date -- action_report_time (Optional, Default value is conversion) It specifies the principle for conversion reporting. -- swipe_up_attribution_window (Optional, Default value is 1_DAY) This is the attribution window for swipe up. -- view_attribution_window (Optional, Default value is 28_DAY) This is the attribution window for views. +- Client ID +- Client Secret +- Refresh Token + ## Setup guide ### Step 1: Set up Snapchat -1. [Set up Snapchat Business account](https://businesshelp.snapchat.com/s/article/get-started?language=en_US) +1. [Set up a Snapchat Business account](https://businesshelp.snapchat.com/s/article/get-started?language=en_US) @@ -38,25 +34,32 @@ This page guides you through the process of setting up the Snapchat Marketing so 2. [Activate Access to the Snapchat Marketing API](https://businesshelp.snapchat.com/s/article/api-apply?language=en_US) 3. Add the OAuth2 app: - Adding the OAuth2 app requires the `redirect_url` parameter. - - If you have the API endpoint that will handle next OAuth process - write it to this parameter. - - If not - just use some valid url. Here's the discussion about it: [Snapchat Redirect URL - Clarity in documentation please](https://github.com/Snap-Kit/bitmoji-sample/issues/3) - - save **Client ID** and **Client Secret** -4. Get refresh token using OAuth2 authentication workflow: - - Open the authorize link in a browser: [https://accounts.snapchat.com/login/oauth2/authorize?response_type=code&client_id=CLIENT_ID&redirect_uri=REDIRECT_URI&scope=snapchat-marketing-api&state=wmKkg0TWgppW8PTBZ20sldUmF7hwvU](https://accounts.snapchat.com/login/oauth2/authorize?response_type=code&client_id=CLIENT_ID&redirect_uri=REDIRECT_URI&scope=snapchat-marketing-api&state=wmKkg0TWgppW8PTBZ20sldUmF7hwvU) + - If you have the API endpoint that will handle next OAuth process, write it to this parameter. + - If you do not have the API endpoint, simply use a valid URL.Refer to the discussion here for more information: [Snapchat Redirect URL - Clarity in documentation please](https://github.com/Snap-Kit/bitmoji-sample/issues/3) + - Save the **Client ID** and **Client Secret** +4. Obtain a refresh token using OAuth2 authentication workflow. + - Open the authorize link in a browser. It will look similar to this: + ``` + https://accounts.snapchat.com/login/oauth2/authorize?response_type=code&client_id=CLIENT_ID&redirect_uri=REDIRECT_URI&scope=snapchat-marketing-api&state=wmKkg0TWgppW8PTBZ20sldUwerf-m + ``` - Login & Authorize via UI - - Locate "code" query parameter in the redirect - - Exchange code for access token + refresh token - `text - curl -X POST \ + - Locate the `code` query parameter in the redirect + - Exchange the `code` for an access token and refresh token. + + Your request will appear similar to the following: + + ```text + curl -X POST \ -d "code={one_time_use_code}" \ -d "client_id={client_id}" \ -d "client_secret={client_secret}" \ -d "grant_type=authorization_code" \ -d "redirect_uri=redirect_uri" - https://accounts.snapchat.com/login/oauth2/access_token - ` - You will receive the API key and refresh token in response. Use this refresh token in the connector specifications. - The useful link to Authentication process is [here](https://marketingapi.snapchat.com/docs/#authentication) + https://accounts.snapchat.com/login/oauth2/access_token` + ``` + +For more information on authenticating into the Snapchat API, read their documentation [here](https://marketingapi.snapchat.com/docs/#authentication) + You will receive the API key and refresh token in the response. Use this refresh token for the connector. ### Step 2: Set up the source connector in Airbyte @@ -68,54 +71,70 @@ This page guides you through the process of setting up the Snapchat Marketing so 1. [Log into your Airbyte Cloud](https://cloud.airbyte.com/workspaces) account. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Snapchat Marketing** from the Source type dropdown and enter a name for this connector. -4. lick `Authenticate your account`. -5. Log in and Authorize to the Snapchat account -6. Choose required Start date -7. click `Set up source`. +4. Click `Authenticate your account`. +5. In the authentication window, log in and authorize access to your Snapchat account +6. (Optional) Choose a Start Date. All data created on or after this date will be synced. If left blank, all records will be synced. + +:::tip +The `Start Date` is required for the all streams that use `start_time` as a key (see Supported Streams section below). +::: +7. (Optional) Choose an End Date. All data created on or before this date will be synced. If left blank, all records will be synced. +8. (Optional) Choose the `Action Report Time`, which specifies how conversions are reported. The default is set to `conversion`, and can be modified to `impression`. +9. (Optional) Choose the 'Swip Up Attribution Window', which specifies the length of the attribution window for swipe up actions. The default is 28 days and can be adjusted. +10. (Optional) Choose the `View Attribution Window`, which specifies the length of the attribution window for views. The default is 28 days and can be adjusted. +11. Click 'Set up source' **For Airbyte Open Source:** -1. Go to local Airbyte page. +1. Open the Airbyte UI. 2. In the left navigation bar, click **Sources**. In the top-right corner, click **+ new source**. 3. On the source setup page, select **Snapchat Marketing** from the Source type dropdown and enter a name for this connector. -4. Add **Client ID**, **Client Secret**, **Refresh Token** -5. Choose required Start date -6. Click `Set up source`. +4. Add the **Client ID**, **Client Secret**, and **Refresh Token** obtained from the setup. +5. (Optional) Choose a Start Date. All data created on or after this date will be synced. If left blank, all records will be synced. + +:::tip +The `Start Date` is required for the all streams that use `start_time` as a key (see Supported Streams section below). +::: +6. (Optional) Choose an End Date. All data created on or before this date will be synced. +7. (Optional) Choose the `Action Report Time`, which specifies how conversions are reported. The default is set to `conversion`, and can be modified to `impression`. +8. (Optional) Choose the 'Swip Up Attribution Window', which specifies the length of the attribution window for swipe up actions. The default is 28 days and can be adjusted. +9. (Optional) Choose the `View Attribution Window`, which specifies the length of the attribution window for views. The default is 28 days and can be adjusted. +10. Click 'Set up source' ## Supported streams and sync modes | Stream | Incremental | Key | |:------------------------|:------------|-------------------------------------| -| Adaccounts | Yes | "id" | +| AdAccounts | Yes | "id" | | Ads | Yes | "id" | -| Adsquads | Yes | "id" | +| AdSquads | Yes | "id" | | Campaigns | Yes | "id" | | Creatives | Yes | "id" | | Media | Yes | "id" | | Organizations | Yes | "id" | | Segments | Yes | "id" | -| AdaccountsStatsHourly | Yes | ["id", "granularity", "start_time"] | -| AdaccountsStatsDaily | Yes | ["id", "granularity", "start_time"] | -| AdaccountsStatsLifetime | No | ["id", "granularity"] | -| AdsStatsHourly | Yes | ["id", "granularity", "start_time"] | -| AdsStatsDaily | Yes | ["id", "granularity", "start_time"] | -| AdsStatsLifetime | No | ["id", "granularity"] | -| AdsquadsStatsHourly | Yes | ["id", "granularity", "start_time"] | -| AdsquadsStatsDaily | Yes | ["id", "granularity", "start_time"] | -| AdsquadsStatsLifetime | No | ["id", "granularity"] | -| CampaignsStatsHourly | Yes | ["id", "granularity", "start_time"] | -| CampaignsStatsDaily | Yes | ["id", "granularity", "start_time"] | -| CampaignsStatsLifetime | No | ["id", "granularity"] | +| AdAccounts_Stats_Hourly | Yes | ["id", "granularity", "start_time"] | +| AdAccounts_Stats_Daily | Yes | ["id", "granularity", "start_time"] | +| AdAccounts_Stats_Lifetime | No | ["id", "granularity"] | +| Ads_Stats_Hourly | Yes | ["id", "granularity", "start_time"] | +| Ads_Stats_Daily | Yes | ["id", "granularity", "start_time"] | +| Ads_Stats_Lifetime | No | ["id", "granularity"] | +| AdSquads_Stats_Hourly | Yes | ["id", "granularity", "start_time"] | +| AdSquads_Stats_Daily | Yes | ["id", "granularity", "start_time"] | +| AdSquads_Stats_Lifetime | No | ["id", "granularity"] | +| Campaigns_Stats_Hourly | Yes | ["id", "granularity", "start_time"] | +| Campaigns_Stats_Daily | Yes | ["id", "granularity", "start_time"] | +| Campaigns_Stats_Lifetime | No | ["id", "granularity"] | ## Performance considerations -Hourly streams can be slowly because they generate a lot of records. +The Snapchat Marketing API limits requests to 1,000 items per page. -Snapchat Marketing API has limitations to 1000 items per page. +Syncing data with an hourly granularity often generates large data volumes and can take longer times to sync. We recommend syncing at a day granularity. ## Changelog diff --git a/docs/managing-airbyte/assets/connector-version-banner.png b/docs/managing-airbyte/assets/connector-version-banner.png new file mode 100644 index 00000000000..abdb78b643a Binary files /dev/null and b/docs/managing-airbyte/assets/connector-version-banner.png differ diff --git a/docs/managing-airbyte/connector-updates.md b/docs/managing-airbyte/connector-updates.md index 817a318db3e..4d5394dec32 100644 --- a/docs/managing-airbyte/connector-updates.md +++ b/docs/managing-airbyte/connector-updates.md @@ -1,3 +1,7 @@ +--- +products: oss-community, oss-enterprise +--- + # Managing Connector Updates in Airbyte While maintaining an Airbyte instance, you'll need to manage connector updates. These are essential for improved functionality, reliability, and compatibility over time. Our team and community contributors are dedicated to maintaining up-to-date connectors. Reasons for updates can be broadly categorized into bug fixes, new features, and changes that impact the user experience or the functionality of the connector. @@ -28,16 +32,15 @@ Each connector's changelog details its update history. You can find it in the [c ### Airbyte Cloud **Minor and Patch Updates:** These are applied automatically and immediately to your instance. You don't need to take any action. -**Major Updates:** These are opt-in. You'll receive notifications about major updates and have a deadline to apply them. If you choose not to opt-in by the deadline, any syncs using the affected connector will be paused to prevent compatibility issues. +**Major Updates:** These are opt-in during a specified timeframe to give you a window to prepare for the change. Airbyte will alert you of a new major version that includes a breaking change, but continue to sync until the cutoff date for upgrade. If you choose not to opt-in by the deadline, any syncs using the affected connector will be paused to prevent compatibility issues. Examples of major version changes are listed in our [breaking change documentation]./using-airbyte/schema-change-management#resolving-breaking-changes) -Updates involving a breaking change will be called out in the UI. The example below shows a prompt that you might see if a connector needs upgrading. Note there is a deadline associated with this upgrade and a link to further guidance on completing the upgrade. - -![Upgrade Path](../release_notes/assets/airbyte_destinations_v2_upgrade_prompt.png) +Updates involving a breaking change will be called out in the UI. The example below shows a prompt that you might see if a connector has passed its cutoff date for upgrade. +![Upgrade Path](assets/connector-version-banner.png) ## Airbyte Open Source (OSS) and Self-Managed Enterprise (SME) -It's good practice to ensure that you are using an updated version of Airbyte when updating connections. +Airbyte recommends using an updated version of Airbyte when updating connections. **All Updates (Major, Minor, Patch):** These are opt-in via the settings page. You'll see a badge in the sidebar indicating available updates. diff --git a/docs/using-airbyte/core-concepts/readme.md b/docs/using-airbyte/core-concepts/readme.md index c081ddc040f..aaf5c554237 100644 --- a/docs/using-airbyte/core-concepts/readme.md +++ b/docs/using-airbyte/core-concepts/readme.md @@ -87,7 +87,7 @@ Read more about each [sync mode](/using-airbyte/core-concepts/sync-modes/README. ## Resumability -[Resumability](/understanding-airbyte/resumability.md) is an important principle in Airbyte's approach to reliability. +[Resumability](/understanding-airbyte/resumability.md) is an important principle in Airbyte's approach to reliability. To ensure your syncs run smoothly with minimal maintenance, we checkpoint a sync's progress and automatically re-attempt the sync under the hood. ## Typing and Deduping diff --git a/docs/using-airbyte/getting-started/add-a-destination.md b/docs/using-airbyte/getting-started/add-a-destination.md index db309ad1705..cd4e186f763 100644 --- a/docs/using-airbyte/getting-started/add-a-destination.md +++ b/docs/using-airbyte/getting-started/add-a-destination.md @@ -36,7 +36,7 @@ Read more about the [specific limitations](/integrations/destinations/google-she Authenticate into your Google account by clicking "Sign in with Google" and granting permissions to Airbyte. Because this is a simple Google Sheets destination, there is only one more required field, **Spreadsheet Link**. This is the path to your spreadsheet that can be copied directly from your browser. - + As an example, we'll be setting up a simple JSON file that will be saved on our local system as the destination. Select **Local JSON** from the list of destinations. This will take you to the destination setup page. The left half of the page contains a set of fields that you will have to fill out. In the **Destination name** field, you can enter a name of your choosing to help you identify this instance of the connector. By default, this will be set to the name of the destination (i.e., `Local JSON`). diff --git a/docs/using-airbyte/getting-started/readme.md b/docs/using-airbyte/getting-started/readme.md index 8d6dbe0285f..26305c31337 100644 --- a/docs/using-airbyte/getting-started/readme.md +++ b/docs/using-airbyte/getting-started/readme.md @@ -8,9 +8,9 @@ Airbyte is an open-source data integration platform designed to help you consoli Whether you're part of a large organization managing complex data pipelines or an individual analyst consolidating data for a personal project, Airbyte can work for you! We offer flexibility and scalability that's easy to tailor to your specific needs, from one-off jobs to enterprise-grade solutions. -There are two options to consider for running Airbyte: +There are two options to consider to run Airbyte: - **Airbyte Cloud** (recommended): allows you to focus on moving data while we take care of managing the infrastructure. -- **Self-managed Airbyte**: can be deployed either locally or in an infrastructure you've set up. Our OSS can be used as a free Community product or implemented with support of Enterprise operations. +- **Self-Managed Airbyte**: can be deployed either locally or in an infrastructure you've set up. Our Self-Managed solution can be used as a free Community product or implemented with support of Enterprise operations. :::tip If you have already deployed Airbyte or you've signed up to use Airbyte Cloud, and you're familiar with [Airbyte's core concepts](../../using-airbyte/core-concepts/), jump ahead to [Building Connections](../../cloud/managing-airbyte-cloud/configuring-connections.md). @@ -24,7 +24,7 @@ Airbyte Cloud offers a 14-day free trial that begins after your first successful To start setting up a data pipeline, see how to [set up a source](./add-a-source.md). -## Open Source Community (OSS) +## Self-Managed Community (OSS) When self-managing Airbyte, your data never leaves your premises. You can use our [OSS Quickstart](oss-quickstart.md) to get started immediately by deploying locally using abctl. @@ -34,10 +34,10 @@ If you're trying Airbyte out for the first time, we'd recommend you sign up for To deploy Airbyte in production, Airbyte recommends deploying on [Kubernetes via Helm](../../deploying-airbyte/on-kubernetes-via-helm.md). -## Open Source Enterprise +## Self-Managed Enterprise Airbyte Self-Managed Enterprise is the most robust way to run Airbyte yourself. With this option, you'll have access to all 300+ pre-built connectors and data will never need to leave your environment. Enterprise setup means that Airbyte becomes self-serve in your organization with new tools to manage multiple users, and the ability to set up multiple teams using Airbyte all in one place. :::tip -To start with Self-Managed Enterprise, you'll need a licence key. [Talk to sales](https://airbyte.com/company/talk-to-sales) to get started with Enterprise. For more details, review our [Enterprise setup guide](/enterprise-setup/README.md). +To start with Self-Managed Enterprise, you'll need a license key. [Talk to sales](https://airbyte.com/company/talk-to-sales) to get started with Enterprise. For more details, review our [Enterprise setup guide](/enterprise-setup/README.md). ::: \ No newline at end of file diff --git a/docs/using-airbyte/getting-started/set-up-a-connection.md b/docs/using-airbyte/getting-started/set-up-a-connection.md index a8f97e3cb82..ed93bee22b8 100644 --- a/docs/using-airbyte/getting-started/set-up-a-connection.md +++ b/docs/using-airbyte/getting-started/set-up-a-connection.md @@ -61,7 +61,7 @@ Once the first sync has completed, you can verify the sync has completed by chec If you followed along and created your own connection using a **Google Sheets** destination, you will now see three tabs created in your Google Sheet, `products`, `users`, and `purchases`. - + If you followed along and created your own connection using a `Local JSON` destination, you can use this command to check the file's contents to make sure the replication worked as intended (be sure to replace YOUR_PATH with the path you chose in your destination setup, and YOUR_STREAM_NAME with the name of an actual stream you replicated): ```bash