Releases: Azure/azure-dev
azure-dev-vscode_0.5.0
0.5.0 (2023-04-05)
Features Added
- [#1849] Support for the
azd package
command has been added for both the entire application and individual services.
Breaking Changes
azure-dev-cli_0.8.0-beta.1
0.8.0-beta.1 (2023-04-10)
Features Added
- [#1715] Adding feature alpha toggle:
- Moving terraform provider as alpha feature. Use
azd config set alpha.terraform on
to have it enabled.
- Moving terraform provider as alpha feature. Use
- [#1833] Deploy from existing package using
--from-package
flag.
Breaking Changes
- [#1715] Using
terraform
as provisioning provider will fail and require user to enable terraform runningazd config set alpha.terraform on
. - [#1801] Restructuring specific command flags.
azd up
no longer runsazd init
. As a result, the following flags have been removed fromazd up
:--template
/-t
--location
/-l
--branch
/-b
--subscription
- Use of
--service
and--no-progress
inazd up
is being deprecated. azd deploy
now accepts a positional argument. Useazd deploy <web>
instead ofazd deploy --service <web>
- Deprecate
--no-progress
flag as it currently does nothing. A warning message is shown when used. - Hide
--output
flag in the usage printout to correctly reflect the current it's current alpha-preview status. The output contract for structured schema such as JSON has yet been finalized.
- [#1804] Adjust command aliases.
azd login
andazd logout
are now available asazd auth login
andazd auth logout
respectively.azd login
andazd logout
are still available for use, but will be removed in a future release.azd infra create
andazd infra delete
, which have always been aliases forazd provision
andazd down
, are now deprecated. The commands are still available for use, but will be removed in a future release.
- [#1824] Add working directory sensitivity for
restore
anddeploy
.azd deploy
will now deploy the current service, when the current working directory is set to a service directory.azd deploy
will deploy all services, when the current working directory is set to the project directory containingazure.yaml
- In other directories,
azd deploy
will not attempt a deployment and instead error out with suggestions.azd deploy --all
can be used to deploy all services, orazd deploy <service>
to deploy a given service always.
- [#1752] Ask fewer questions during
init
.azd init
will now only prompt for the environment name. Azure subscription and location values are prompted only when infrastructure provisioning is needed, when runningazd provision
, and consequently when runningazd up
.
Bugs Fixed
- [#1734] Fix setting
AZURE_PRINCIPAL_ID
on multi-tenant directory. - [#1738] Fix generating auth token on multi-tenant directory.
- [#1762] Allow local files to be kept when running
init
. - [#1764] Enhance zip-deploy during build for:
- Python: Do not include virtual environments for python.
- Node: Update node modules detection to exclude it from build.
- [#1857] Adds
package
command hooks to azd schema. - [#1878] Ensure default generated docker repo/tags are all lowercase.
- [#1875] Fixes panic for
postpackage
hook errors.
Other Changes
azd up
no longer runs azd init
The behavior of azd up -t <template>
can be reproduced with:
cd <empty dir>
azd init -t <template>
azd up
azd deploy
no longer deploys all services when ran in any directory
The new behavior is as follows:
azd deploy
will now deploy the current service, when the current working directory is set to a service directory.azd deploy
will deploy all services, when the current working directory is set to the project directory containingazure.yaml
.- In other directories,
azd deploy
will not attempt a deployment and error out with suggestions.azd deploy --all
can be used to deploy all services, orazd deploy <service>
to deploy a given service always.
azd up
ordering
azd up
now packages artifacts prior to running azd provision
and azd deploy
. This should not affect most users, with the exception of users that may be taking advantage of azd
's environment values in packaging staticwebapp
services. If azd up
no longer works as expected, and you are currently taking advantage of azd
's provided environment values to package your application, a predeploy
hook may be used to generate configuration files from azd
environment values. See the working example in our ToDo templates that leverage staticwebapp
, example here. Note that script hooks
automatically have azd
environment values loaded in the shell environment.
azure-dev-vscode_0.4.2
0.4.2 (2023-03-15)
Bugs Fixed
- [#1735] Fixed an issue with the login command not working immediately after install.
azure-dev-vscode_0.4.1
0.4.1 (2023-03-14)
Bugs Fixed
- [#1724] Refine conditions for displaying the prompt to install the CLI.
azure-dev-vscode_0.4.0
0.4.0 (2023-03-08)
Added
- [#853] Integration with the Azure Resources extension's workspace view. Requires version 0.6.1 of the Azure Resources extension.
- [#1644] Added a walkthrough experience for using the extension.
azure-dev-cli_0.7.0-beta.1
0.7.0-beta.1 (2023-03-09)
Features Added
- [#1515] Remove gh-cli as external dependency for
azd pipeline config
. - [#1558] Upgrade bicep version to 0.14.46 and fetch ARM specific version on ARM platforms.
- [#1611] Updated formatting for displaying command's help.
- [#1629] Add support for Azure Kubernetes Service (AKS) target.
Bugs Fixed
- [#1631] Fail fast during
azd init
whengit
is not installed. - [#1559] No feedback output during provisioning some templates.
- [#1683] Fix
azd pipeline config
to honor provider fromazure.yaml
. - [#1578] Fix crash while running
azd login
, due to a tenantDisplayName
being nil.
Thanks to community members: @pamelafox, @tonybaloney, @cobey for their contributions in this release.
azure-dev-cli_0.6.0-beta.2
0.6.0-beta.2 (2023-02-10)
Bugs Fixed
- [#1527] Fix running specific commands with
--output json
causing stack overflow errors to occur. - [#1534] Fix running commands with
-e <environment name>
flag or withAZURE_ENV_NAME
set not being respected. When running in CI environments, this caused prompting to occur, and failing if--no-prompt
is specified.
azure-dev-cli_0.6.0-beta.1
0.6.0-beta.1 (2023-02-08)
Features Added
-
[#1236] Support for command and service hooks
-
[#1414] Support for installation via Homebrew. Windows Package Manager, and Chocolatey are also now supported.
-
[#1407] Improve UX styling for
azd pipeline config
. -
[#1478] Support for multiple Azure tenants.
-
[#1345] Core bicep module
appservice.bicep
now supportsftpsState
as a parameter to configure FTPS upload behavior. -
[#1497] Core bicep module
appservice.bicep
now supportshealthCheckPath
as a parameter to configure the health-check endpoint. -
[#1403] Core bicep module
apim-api.bicep
now links Web App or Function App instances. This allows users on the Azure Portal to navigate to the API management resource directly from the Web App or Function App.
Bugs Fixed
- [#1406] On Windows, fix MSI installation not updating
azd
in some cases (reported by @lechnerc77, fixed by @heaths) - [#1418] Display
provision
progress for PostgreSQL server resources. - [#1483] For Python projects, skip packaging of virtual environment (
.venv
folders) - [#1495]
init
now restores file executable permissions and initializes agit
repository automatically. - [#1470] Improve performance of
azd --help
on Windows for domain-joined users. - [#1503] Fix display for Function App types in
provision
progress
Thanks to community members: @pamelafox, @lechnerc77 for their contributions in this release.
azure-dev-cli_0.5.0-beta.3
azure-dev-cli_0.5.0-beta.2
0.5.0-beta.2 (2023-01-12)
Bugs Fixed
- [#1366] Login not possible with personal account after upgrade to 0.5.0.