A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.microsoft.com/en-us/azure/developer/azure-developer-cli/remote-environments-support below:

Remote Environments Support | Microsoft Learn

How do remote environments work?

To use remote environments, you can enable remote state to ensure the environment state automatically persists to the configured remote store. Meaning any azd command that writes to your azd .env or config.json file will automatically persist.

Configure remote state

Remote state for azd can be configured globally in azd's config.json or by project within the azure.yaml. If remote state is not set up, environment values and configuration continue to be stored locally.

You can configure remote state within the state.remote element of azd configuration

Enable by project azure.yaml
name: azd-project-name
state:
  remote:
    backend: AzureBlobStorage
    config:
      accountName: saazdremotestate
      containerName: myproject # Defaults to project name if not specified
Enable globally azd config.json
{
  "state": {
    "remote": {
      "backend": "AzureBlobStorage",
      "config": {
        "accountName": "saazdremotestate"
      }
    }
  }
}
Supported Remote state backends Azure Blob Storage

azd writes .env and config.json files to an Azure storage blob container

Configuration Remote state and azd commands azd env list

Lists all local and remote environments available. For example:

azd env select

When selecting an environment that does not exist locally, the remote state is copied to a new local environment.

For example, consider the output from azd env list above. To copy the remote state, dev to your local environment you would run the following:

azd env select dev

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4