azure-dev icon indicating copy to clipboard operation
azure-dev copied to clipboard

Update the infra/core modules to AVM modules

Open Menghua1 opened this issue 1 year ago • 19 comments

Fixes: https://github.com/Azure/azure-dev/issues/3327

@jongio for notification.

Menghua1 avatar Jun 04 '24 09:06 Menghua1

@jongio Based on your suggestion, the code has been updated. Please review, thanks.

Menghua1 avatar Jun 06 '24 08:06 Menghua1

/azp run azure-dev - repoman

v-xuto avatar Jun 19 '24 08:06 v-xuto

Azure Pipelines successfully started running 1 pipeline(s).

azure-pipelines[bot] avatar Jun 19 '24 08:06 azure-pipelines[bot]

The new AVM for keyvault has default parameter enablePurgeProtection: true , which is different from the default false default on Microsoft.KeyVault/vaults@2022-07-01 (the default is null there, keeping purge protection off).

Added a new commit here to set purge protection off as it is currently w/o AVMs.

This fixed an issue on EngSys where deleted KV accounts can't be removed due to the protection.

@jongio , should the default parameter on AVM be false (instead of true?) Why is it forcing purge protection by default?

@benbp, FYI

vhvb1989 avatar Jul 08 '24 21:07 vhvb1989

Azure Dev CLI Install Instructions

Install scripts

MacOS/Linux

May elevate using sudo on some platforms and configurations

bash:

curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976 --version '' --verbose --skip-verify

pwsh:

Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/uninstall-azd.ps1' -OutFile uninstall-azd.ps1; ./uninstall-azd.ps1
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/install-azd.ps1' -OutFile install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976' -Version '' -SkipVerify -Verbose

Windows

PowerShell install

powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976' -Version '' -SkipVerify -Verbose;"

MSI install

powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/azd-windows-amd64.msi' -OutFile azd-windows-amd64.msi; msiexec /i azd-windows-amd64.msi /qn"

Standalone Binary

  • Linux -
    • x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/azd-linux-amd64.tar.gz
    • ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/azd-linux-arm64.tar.gz
  • MacOS -
    • x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/azd-darwin-amd64.zip
    • ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/azd-darwin-arm64.zip
  • Windows -
    • x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/azd-windows-amd64.zip
    • ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/azd-windows-arm64-alpha.zip

MSI

  • x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3976/azd-windows-amd64.msi

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference description: This article explains the syntax and parameters for the various Azure Developer CLI commands. author: alexwolfmsft ms.author: alexwolf ms.date: 07/08/2024 ms.service: azure-dev-cli ms.topic: conceptual ms.custom: devx-track-azdevcli

Azure Developer CLI reference

This article explains the syntax and parameters for the various Azure Developer CLI commands.

azd

The Azure Developer CLI (azd) is an open-source tool that helps onboard and manage your application on Azure

Options

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --docs         Opens the documentation for azd in your web browser.
  -h, --help         Gets help for azd.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd auth: Authenticate with Azure.
  • azd config: Manage azd configurations (ex: default Azure subscription, location).
  • azd deploy: Deploy the application's code to Azure.
  • azd down: Delete Azure resources for an application.
  • azd env: Manage environments.
  • azd hooks: Develop, test and run hooks for an application. (Beta)
  • azd init: Initialize a new application.
  • azd monitor: Monitor a deployed application. (Beta)
  • azd package: Packages the application's code to be deployed to Azure. (Beta)
  • azd pipeline: Manage and configure your deployment pipelines. (Beta)
  • azd provision: Provision the Azure resources for an application.
  • azd restore: Restores the application's dependencies. (Beta)
  • azd show: Display information about your app and its resources.
  • azd template: Find and view template details. (Beta)
  • azd up: Provision Azure resources, and deploy your project with a single command.
  • azd version: Print the version number of Azure Developer CLI.

azd auth

Authenticate with Azure.

Options

      --docs   Opens the documentation for azd auth in your web browser.
  -h, --help   Gets help for auth.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd auth login: Log in to Azure.
  • azd auth logout: Log out of Azure.
  • Back to top

azd auth login

Log in to Azure.

Synopsis

Log in to Azure.

When run without any arguments, log in interactively using a browser. To log in using a device code, pass --use-device-code.

To log in as a service principal, pass --client-id and --tenant-id as well as one of: --client-secret, --client-certificate, or --federated-credential-provider.

To log in using a managed identity, pass --managed-identity, which will use the system assigned managed identity. To use a user assigned managed identity, pass --client-id in addition to --managed-identity with the client id of the user assigned managed identity you wish to use.

azd auth login [flags]

Options

      --check-status                           Checks the log-in status instead of logging in.
      --client-certificate string              The path to the client certificate for the service principal to authenticate with.
      --client-id string                       The client id for the service principal to authenticate with.
      --client-secret string                   The client secret for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --docs                                   Opens the documentation for azd auth login in your web browser.
      --federated-credential-provider string   The provider to use to acquire a federated token to authenticate with.
  -h, --help                                   Gets help for login.
      --managed-identity                       Use a managed identity to authenticate.
      --redirect-port int                      Choose the port to be used as part of the redirect URI during interactive login.
      --tenant-id string                       The tenant id or domain name to authenticate with.
      --use-device-code[=true]                 When true, log in by using a device code instead of a browser.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd auth: Authenticate with Azure.
  • Back to top

azd auth logout

Log out of Azure.

Synopsis

Log out of Azure

azd auth logout [flags]

Options

      --docs   Opens the documentation for azd auth logout in your web browser.
  -h, --help   Gets help for logout.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd auth: Authenticate with Azure.
  • Back to top

azd config

Manage azd configurations (ex: default Azure subscription, location).

Synopsis

Manage the Azure Developer CLI user configuration, which includes your default Azure subscription and location.

Available since azure-dev-cli_0.4.0-beta.1.

The easiest way to configure azd for the first time is to run azd init. The subscription and location you select will be stored in the config.json file located in the config directory. To configure azd anytime afterwards, you'll use azd config set.

The default value of the config directory is:

  • $HOME/.azd on Linux and macOS
  • %USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.

Options

      --docs   Opens the documentation for azd config in your web browser.
  -h, --help   Gets help for config.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd config get: Gets a configuration.
  • azd config list-alpha: Display the list of available features in alpha stage.
  • azd config reset: Resets configuration to default.
  • azd config set: Sets a configuration.
  • azd config show: Show all the configuration values.
  • azd config unset: Unsets a configuration.
  • Back to top

azd config get

Gets a configuration.

Synopsis

Gets a configuration in the configuration path.

The default value of the config directory is:

  • $HOME/.azd on Linux and macOS
  • %USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.

azd config get <path> [flags]

Options

      --docs   Opens the documentation for azd config get in your web browser.
  -h, --help   Gets help for get.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd config: Manage azd configurations (ex: default Azure subscription, location).
  • Back to top

azd config list-alpha

Display the list of available features in alpha stage.

azd config list-alpha [flags]

Options

      --docs   Opens the documentation for azd config list-alpha in your web browser.
  -h, --help   Gets help for list-alpha.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd config: Manage azd configurations (ex: default Azure subscription, location).
  • Back to top

azd config reset

Resets configuration to default.

Synopsis

Resets all configuration in the configuration path.

The default value of the config directory is:

  • $HOME/.azd on Linux and macOS
  • %USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable to the default.

azd config reset [flags]

Options

      --docs    Opens the documentation for azd config reset in your web browser.
  -f, --force   Force reset without confirmation.
  -h, --help    Gets help for reset.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd config: Manage azd configurations (ex: default Azure subscription, location).
  • Back to top

azd config set

Sets a configuration.

Synopsis

Sets a configuration in the configuration path.

The default value of the config directory is:

  • $HOME/.azd on Linux and macOS
  • %USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.

azd config set <path> <value> [flags]

Examples

azd config set defaults.subscription <yourSubscriptionID>
azd config set defaults.location eastus

Options

      --docs   Opens the documentation for azd config set in your web browser.
  -h, --help   Gets help for set.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd config: Manage azd configurations (ex: default Azure subscription, location).
  • Back to top

azd config show

Show all the configuration values.

Synopsis

Show all configuration values in the configuration path.

The default value of the config directory is:

  • $HOME/.azd on Linux and macOS
  • %USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.

azd config show [flags]

Options

      --docs   Opens the documentation for azd config show in your web browser.
  -h, --help   Gets help for show.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd config: Manage azd configurations (ex: default Azure subscription, location).
  • Back to top

azd config unset

Unsets a configuration.

Synopsis

Removes a configuration in the configuration path.

The default value of the config directory is:

  • $HOME/.azd on Linux and macOS
  • %USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.

azd config unset <path> [flags]

Examples

azd config unset defaults.location

Options

      --docs   Opens the documentation for azd config unset in your web browser.
  -h, --help   Gets help for unset.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd config: Manage azd configurations (ex: default Azure subscription, location).
  • Back to top

azd deploy

Deploy the application's code to Azure.

azd deploy <service> [flags]

Options

      --all                   Deploys all services that are listed in azure.yaml
      --docs                  Opens the documentation for azd deploy in your web browser.
  -e, --environment string    The name of the environment to use.
      --from-package string   Deploys the application from an existing package.
  -h, --help                  Gets help for deploy.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd down

Delete Azure resources for an application.

azd down [flags]

Options

      --docs                 Opens the documentation for azd down in your web browser.
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for down.
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd env

Manage environments.

Options

      --docs   Opens the documentation for azd env in your web browser.
  -h, --help   Gets help for env.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd env get-values: Get all environment values.
  • azd env list: List environments.
  • azd env new: Create a new environment and set it as the default.
  • azd env refresh: Refresh environment settings by using information from a previous infrastructure provision.
  • azd env select: Set the default environment.
  • azd env set: Manage your environment settings.
  • Back to top

azd env get-values

Get all environment values.

azd env get-values [flags]

Options

      --docs                 Opens the documentation for azd env get-values in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-values.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd env: Manage environments.
  • Back to top

azd env list

List environments.

azd env list [flags]

Options

      --docs   Opens the documentation for azd env list in your web browser.
  -h, --help   Gets help for list.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd env: Manage environments.
  • Back to top

azd env new

Create a new environment and set it as the default.

azd env new <environment> [flags]

Options

      --docs                  Opens the documentation for azd env new in your web browser.
  -h, --help                  Gets help for new.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd env: Manage environments.
  • Back to top

azd env refresh

Refresh environment settings by using information from a previous infrastructure provision.

azd env refresh <environment> [flags]

Options

      --docs                 Opens the documentation for azd env refresh in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.
      --hint string          Hint to help identify the environment to refresh

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd env: Manage environments.
  • Back to top

azd env select

Set the default environment.

azd env select <environment> [flags]

Options

      --docs   Opens the documentation for azd env select in your web browser.
  -h, --help   Gets help for select.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd env: Manage environments.
  • Back to top

azd env set

Manage your environment settings.

azd env set <key> <value> [flags]

Options

      --docs                 Opens the documentation for azd env set in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for set.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd env: Manage environments.
  • Back to top

azd hooks

Develop, test and run hooks for an application. (Beta)

Options

      --docs   Opens the documentation for azd hooks in your web browser.
  -h, --help   Gets help for hooks.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd hooks run: Runs the specified hook for the project and services
  • Back to top

azd hooks run

Runs the specified hook for the project and services

azd hooks run <name> [flags]

Options

      --docs                 Opens the documentation for azd hooks run in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for run.
      --platform string      Forces hooks to run for the specified platform.
      --service string       Only runs hooks for the specified service.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd hooks: Develop, test and run hooks for an application. (Beta)
  • Back to top

azd init

Initialize a new application.

azd init [flags]

Options

  -b, --branch string         The template branch to initialize from. Must be used with a template argument (--template or -t).
      --docs                  Opens the documentation for azd init in your web browser.
  -e, --environment string    The name of the environment to use.
  -f, --filter strings        The tag(s) used to filter template results. Supports comma-separated values.
      --from-code             Initializes a new application from your existing code.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
  -s, --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       Initializes a new application from a template. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd monitor

Monitor a deployed application. (Beta)

azd monitor [flags]

Options

      --docs                 Opens the documentation for azd monitor in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for monitor.
      --live                 Open a browser to Application Insights Live Metrics. Live Metrics is currently not supported for Python apps.
      --logs                 Open a browser to Application Insights Logs.
      --overview             Open a browser to Application Insights Overview Dashboard.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd package

Packages the application's code to be deployed to Azure. (Beta)

azd package <service> [flags]

Options

      --all                  Packages all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd package in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.
      --output-path string   File or folder path where the generated packages will be saved.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd pipeline

Manage and configure your deployment pipelines. (Beta)

Options

      --docs   Opens the documentation for azd pipeline in your web browser.
  -h, --help   Gets help for pipeline.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd pipeline config: Configure your deployment pipeline to connect securely to Azure. (Beta)
  • Back to top

azd pipeline config

Configure your deployment pipeline to connect securely to Azure. (Beta)

azd pipeline config [flags]

Options

  -m, --applicationServiceManagementReference string   Service Management Reference. References application or service contact information from a Service or Asset Management database. This value must be a Universally Unique Identifier (UUID). You can set this value globally by running azd config set pipeline.config.applicationServiceManagementReference <UUID>.
      --auth-type string                               The authentication type used between the pipeline provider and Azure for deployment (Only valid for GitHub provider). Valid values: federated, client-credentials.
      --docs                                           Opens the documentation for azd pipeline config in your web browser.
  -e, --environment string                             The name of the environment to use.
  -h, --help                                           Gets help for config.
      --principal-id string                            The client id of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-name string                          The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role stringArray                     The roles to assign to the service principal. By default the service principal will be granted the Contributor and User Access Administrator roles. (default [Contributor,User Access Administrator])
      --provider string                                The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines).
      --remote-name string                             The name of the git remote to configure the pipeline to run on. (default "origin")

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd pipeline: Manage and configure your deployment pipelines. (Beta)
  • Back to top

azd provision

Provision the Azure resources for an application.

azd provision [flags]

Options

      --docs                 Opens the documentation for azd provision in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.
      --no-state             Do not use latest Deployment State (bicep only).
      --preview              Preview changes to Azure resources.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd restore

Restores the application's dependencies. (Beta)

azd restore <service> [flags]

Options

      --all                  Restores all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd restore in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for restore.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd show

Display information about your app and its resources.

azd show [flags]

Options

      --docs                 Opens the documentation for azd show in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for show.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd template

Find and view template details. (Beta)

Options

      --docs   Opens the documentation for azd template in your web browser.
  -h, --help   Gets help for template.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd template list: Show list of sample azd templates. (Beta)
  • azd template show: Show details for a given template. (Beta)
  • azd template source: View and manage template sources. (Beta)
  • Back to top

azd template list

Show list of sample azd templates. (Beta)

azd template list [flags]

Options

      --docs             Opens the documentation for azd template list in your web browser.
  -f, --filter strings   The tag(s) used to filter template results. Supports comma-separated values.
  -h, --help             Gets help for list.
  -s, --source string    Filters templates by source.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd template: Find and view template details. (Beta)
  • Back to top

azd template show

Show details for a given template. (Beta)

azd template show <template> [flags]

Options

      --docs   Opens the documentation for azd template show in your web browser.
  -h, --help   Gets help for show.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd template: Find and view template details. (Beta)
  • Back to top

azd template source

View and manage template sources. (Beta)

Options

      --docs   Opens the documentation for azd template source in your web browser.
  -h, --help   Gets help for source.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd template: Find and view template details. (Beta)
  • azd template source add: Adds an azd template source at the specified key (Beta)
  • azd template source list: Lists the configured azd template sources. (Beta)
  • azd template source remove: Removes the specified azd template source (Beta)
  • Back to top

azd template source add

Adds an azd template source at the specified key (Beta)

azd template source add <key> [flags]

Options

      --docs              Opens the documentation for azd template source add in your web browser.
  -h, --help              Gets help for add.
  -l, --location string   Location of the template source.
  -n, --name string       Display name of the template source.
  -t, --type string       Kind of the template source.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd template source: View and manage template sources. (Beta)
  • Back to top

azd template source list

Lists the configured azd template sources. (Beta)

azd template source list [flags]

Options

      --docs   Opens the documentation for azd template source list in your web browser.
  -h, --help   Gets help for list.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd template source: View and manage template sources. (Beta)
  • Back to top

azd template source remove

Removes the specified azd template source (Beta)

azd template source remove <key> [flags]

Options

      --docs   Opens the documentation for azd template source remove in your web browser.
  -h, --help   Gets help for remove.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • azd template source: View and manage template sources. (Beta)
  • Back to top

azd up

Provision Azure resources, and deploy your project with a single command.

azd up [flags]

Options

      --docs                 Opens the documentation for azd up in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for up.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azd version

Print the version number of Azure Developer CLI.

azd version [flags]

Options

      --docs   Opens the documentation for azd version in your web browser.
  -h, --help   Gets help for version.

Options inherited from parent commands

  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

  • Back to top

azure-sdk avatar Jul 09 '24 03:07 azure-sdk

@Menghua1 , you force-pushed your changes erasing my last commit. See my comment: https://github.com/Azure/azure-dev/pull/3976#issuecomment-2215405821.

I have manually cancel the repo-man pipeline to avoid the issues with purgeProtection enabled.

Please disable purge protection from keyvault before running the pipeline again

vhvb1989 avatar Jul 09 '24 06:07 vhvb1989

@Menghua1 , you force-pushed your changes erasing my last commit. See my comment: #3976 (comment).

I have manually cancel the repo-man pipeline to avoid the issues with purgeProtection enabled.

Please disable purge protection from keyvault before running the pipeline again

Sorry, I forced push and deleted your commit. In my latest commit, I have disabled purge protection from keyvault, is that correct?

Menghua1 avatar Jul 09 '24 06:07 Menghua1

@Menghua1 , you force-pushed your changes erasing my last commit. See my comment: #3976 (comment). I have manually cancel the repo-man pipeline to avoid the issues with purgeProtection enabled. Please disable purge protection from keyvault before running the pipeline again

Sorry, I forced push and deleted your commit. In my latest commit, I have disabled purge protection from keyvault, is that correct?

Please make sure you are rebasing from main and getting latest before you push. thx

jongio avatar Jul 09 '24 17:07 jongio

/azp run azure-dev - repoman

v-xuto avatar Jul 11 '24 03:07 v-xuto

Azure Pipelines successfully started running 1 pipeline(s).

azure-pipelines[bot] avatar Jul 11 '24 03:07 azure-pipelines[bot]

Main points:

  • Keyvaults + keyvault access appear to be using the same resource module. Can these be merged
  • Consistency issues with container app if there is an azd provision after azd deploy. Container app gets reset
  • Higher cognitive load to use bicep registry modules vs infra core. Doesn't feel easier / better than using the standard bicep resources.

Maybe a better middle ground solution would be to have a slimmer infra/core that uses bicep registry modules internally to avoid all the bicep configuration bloat in each main.bicep file.

@wbreza For the above points, our ideas are as follows:

  • Keyvaults + keyvault access: They cannot be merged. Because the Module api needs to reference the properties of the Module keyvault. If the Module keyvault also needs to reference the properties of the Module api to add access policies, the Module api and Module keyvault reference each other, forming a closed loop.
  • Consistency issues with container app: Yes, the upsert containerapp module in infra/core handles this inconsistency.. Besides, we have created a ptn module issue. After the issue was fixed, we will use the ptn module to replace it.

Maybe a better middle ground solution would be to have a slimmer infra/core that uses bicep registry modules internally to avoid all the bicep configuration bloat in each main.bicep file.

@jongio What do you think of Wbreza's better middle ground solution?

Menghua1 avatar Aug 29 '24 08:08 Menghua1

What do you think of Wbreza's better middle ground solution?

Let's get some app modules in azure-dev repo, but not in infra/core. They can be part of shared app modules. The idea is to have no infra/core folder, but if we want to put some lightweight helper modules in infra/app, I'm okay with that.

jongio avatar Aug 29 '24 15:08 jongio

What do you think of Wbreza's better middle ground solution?

Let's get some app modules in azure-dev repo, but not in infra/core. They can be part of shared app modules. The idea is to have no infra/core folder, but if we want to put some lightweight helper modules in infra/app, I'm okay with that.

@jongio According to your suggestion, we have now added two shared app modules in infra/app, namely web-avm.bicep and api-avm.bivep. The creation of app service becomes simpler by calling these two shared app modules. Do you think this is okay?

Menghua1 avatar Sep 03 '24 06:09 Menghua1

@jongio According to your suggestion, we have now added two shared app modules in infra/app, namely web-avm.bicep and api-avm.bivep. The creation of app service becomes simpler by calling these two shared app modules. Do you think this is okay?

That uses pm2, which is for node only right? I think we need to look at what azd infra/core has today and potentially bring more of those files over to infra/app. For each of node, python, etc.

jongio avatar Sep 03 '24 18:09 jongio

@jongio web-avm.bicep is applicable to all front-ends using appservice (only for node), api-avm.bivep is applicable to all back-ends using appservice (for all language), and these two files can be applied to all repos using appservice in azure-dev.

In addition, we will migrate all bicep files in infra/core to infra/app. But, there are two questions that need to be confirmed with you:

  1. For ptn modules, these modules are under development. After these ptn modules are fixed, we will start migrating to infra/app, is that ok?
  2. For these modules, such as staticWeb, appServicePlan, storageAccount, logAnalytics, applicationInsights. These modules are non-redundant, lightweight, and have few parameters. Do they also need to be migrated to infra/app?

Menghua1 avatar Sep 05 '24 10:09 Menghua1

@jongio web-avm.bicep is applicable to all front-ends using appservice (only for node), api-avm.bivep is applicable to all back-ends using appservice (for all language), and these two files can be applied to all repos using appservice in azure-dev.

In addition, we will migrate all bicep files in infra/core to infra/app. But, there are two questions that need to be confirmed with you:

  1. For ptn modules, these modules are under development. After these ptn modules are fixed, we will start migrating to infra/app, is that ok?
  2. For these modules, such as staticWeb, appServicePlan, storageAccount, logAnalytics, applicationInsights. These modules are non-redundant, lightweight, and have few parameters. Do they also need to be migrated to infra/app?

Let's update this PR to use the new PTN modules as well so we do all of the move to AVM and the new infra/app modules in one PR.

Let's not wrap any modules that don't need to be wrapped. If they are simple and don't require defaults, then okay to directly reference.

jongio avatar Sep 11 '24 17:09 jongio

@jongio We have wrapped the following five modules into infra/app.

Besides, for modules that are simple and do not need default values, there is no wrapper.

Currently only aks and container-app-upsert have not been migrated yet, because when migrating to avm ptn module, two issues were found, two PRs have been opened for this. PR link is as follows, please review. We will continue the migration after these two PRs are merged.

  • https://github.com/Azure/bicep-registry-modules/pull/3589
  • https://github.com/Azure/bicep-registry-modules/pull/3560

Menghua1 avatar Oct 22 '24 09:10 Menghua1

Does the App Service module that you're using include the right variable for AppInsights connection? The current version in azd does not, see my PR here: https://github.com/Azure/azure-dev/pull/4491/files#diff-69d520add196bb5fa4745a89b2450fa9066de6659da0977c1c3bfdf33da8bc14R95

pamelafox avatar Oct 25 '24 22:10 pamelafox

Does the App Service module that you're using include the right variable for AppInsights connection? The current version in azd does not, see my PR here: https://github.com/Azure/azure-dev/pull/4491/files#diff-69d520add196bb5fa4745a89b2450fa9066de6659da0977c1c3bfdf33da8bc14R95

@pamelafox Not included, but now it has been added to the current PR according to PR4491, relevant commits: https://github.com/Azure/azure-dev/pull/3976/commits/8910cac3efdc3416366894aa17a901d55abb6ef8

Menghua1 avatar Oct 28 '24 08:10 Menghua1

@jongio At present, the migration to AVM has been completed. We have also done some simple testing of all templates locally and they have all been provisioned and deployed successfully.

However, the CI of this pr failed because arm-client-id-test-tenant, arm-client-secret-test-tenant and arm-tenant-id-test-tenant indicate that these environment variables are not set correctly, and there is no browser available to open the URL in the current environment. This is not caused by this pr, please help solve it.

Menghua1 avatar Oct 29 '24 09:10 Menghua1

@jongio At present, the migration to AVM has been completed. We have also done some simple testing of all templates locally and they have all been provisioned and deployed successfully.

However, the CI of this pr failed because arm-client-id-test-tenant, arm-client-secret-test-tenant and arm-tenant-id-test-tenant indicate that these environment variables are not set correctly, and there is no browser available to open the URL in the current environment. This is not caused by this pr, please help solve it.

@vhvb1989 or @danieljurek any thoughts on these failures?

jongio avatar Oct 29 '24 15:10 jongio

@jongio At present, the migration to AVM has been completed. We have also done some simple testing of all templates locally and they have all been provisioned and deployed successfully. However, the CI of this pr failed because arm-client-id-test-tenant, arm-client-secret-test-tenant and arm-tenant-id-test-tenant indicate that these environment variables are not set correctly, and there is no browser available to open the URL in the current environment. This is not caused by this pr, please help solve it.

@vhvb1989 or @danieljurek any thoughts on these failures?

the test-templates pipelines is currently disabled/not-working. @ellismg is working for making it work again. You can only run the test-templates scripts manually for now.

vhvb1989 avatar Oct 29 '24 20:10 vhvb1989

the test-templates pipelines is currently disabled/not-working. @ellismg is working for making it work again. You can only run the test-templates scripts manually for now.

Once the test-templates pipelines work, please let me know and I will re-run the pipeline for this PR.

In addition, we have already run the test-templates scripts manually locally.

Menghua1 avatar Oct 30 '24 06:10 Menghua1

Repoman Generation Results

Repoman pushed changes to remotes for the following projects:

Project: todo-csharp-cosmos-sql

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-csharp-cosmos-sql -b pr/3976

View Changes | Compare Changes


Project: todo-csharp-sql-swa-func

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-csharp-sql-swa-func -b pr/3976

View Changes | Compare Changes


Project: todo-csharp-sql

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-csharp-sql -b pr/3976

View Changes | Compare Changes


Project: todo-java-mongo-aca

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-java-mongo-aca -b pr/3976

View Changes | Compare Changes


Project: todo-java-mongo

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-java-mongo -b pr/3976

View Changes | Compare Changes


Project: todo-nodejs-mongo-aca

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-nodejs-mongo-aca -b pr/3976

View Changes | Compare Changes


Project: todo-nodejs-mongo-aks

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-nodejs-mongo-aks -b pr/3976

View Changes | Compare Changes


Project: todo-nodejs-mongo-swa-func

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-nodejs-mongo-swa-func -b pr/3976

View Changes | Compare Changes


Project: todo-nodejs-mongo

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-nodejs-mongo -b pr/3976

View Changes | Compare Changes


Project: todo-python-mongo-aca

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-python-mongo-aca -b pr/3976

View Changes | Compare Changes


Project: todo-python-mongo-swa-func

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-python-mongo-swa-func -b pr/3976

View Changes | Compare Changes


Project: todo-python-mongo

Remote: azure-samples-staging

Branch: pr/3976

You can initialize this project with:

azd init -t Azure-Samples/todo-python-mongo -b pr/3976

View Changes | Compare Changes


azure-sdk avatar Jan 08 '25 08:01 azure-sdk

@rajeshkamal5050 The ci error has been resolved and the pr is ready, please review it again.

Menghua1 avatar Jan 08 '25 09:01 Menghua1

@vhvb1989 can we get this merged or do you see anything pending?

rajeshkamal5050 avatar Feb 19 '25 05:02 rajeshkamal5050