You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix bug in configure-continuous-deployments command and maintain developer CLI (#684)
### Summary & Motivation
Fix an issue where the `configure-continuous-deployments` command failed
when the `az` CLI threw an exception. Previously, these exceptions were
handled correctly, but a recent update to how the CLI executes commands
introduced an issue where errors were not always caught properly. This
is now fixed.
Additionally, Azure region identifiers have been improved. The previous
region abbreviations (e.g., `gwc` for Germany West Central) were not
always intuitive. These have been updated to use country-specific ISO
codes where applicable (e.g., `us`, `ca`, `uk`), and regional codes for
areas with shared data sovereignty rules (e.g., `eu` for the European
Union, `as` for Southeast Asia).
Other general maintenance updates have also been made to the developer
CLI:
- Ensure consistency in CLI descriptions and output messages by
standardizing trailing periods.
- Upgrade all NuGet packages, .NET SDK, and JetBrains tools to their
latest versions.
- Fix static code analysis warnings from SonarQube and JetBrains.
- Remove `ConfigurationSettings.ConfigurationSetting`, which has been
marked as obsolete for a while.
- Add an explicit reference to System.IO.Pipelines Version=9.0.1 to
avoid having to double build when the CLI detects changes.
### Checklist
- [x] I have added tests, or done manual regression tests
- [x] I have updated the documentation, if necessary
[yellow]** All variables can be changed on the GitHub Settings page. For example, if you want to deploy production or staging to different locations.[/]
521
521
522
522
4. Disable the reusable GitHub workflows [blue]Deploy Container[/] and [blue]Plan and Deploy Infrastructure[/].
- To add a step for manual approval during infrastructure deployment to the staging and production environments, set up required reviewers on GitHub environments. Visit [blue]{Config.GithubInfo!.Url}/settings/environments[/] and enable [blue]Required reviewers[/] for the [bold]staging[/] and [bold]production[/] environments. Requires a paid GitHub plan for private repositories.
873
876
874
877
- Configure the Domain Name for the staging and production environments. This involves two steps:
875
-
878
+
876
879
a. Go to [blue]{Config.GithubInfo!.Url}/settings/variables/actions[/] to set the [blue]DOMAIN_NAME_STAGING[/] and [blue]DOMAIN_NAME_PRODUCTION[/] variables. E.g. [blue]staging.your-saas-company.com[/] and [blue]your-saas-company.com[/].
877
-
880
+
878
881
b. Run the [blue]Cloud Infrastructure - Deployment[/] workflow again. Note that it might fail with an error message to set up a DNS TXT and CNAME record. Once done, re-run the failed jobs.
879
882
880
883
- Set up SonarCloud for code quality and security analysis. This service is free for public repositories. Visit [blue]https://sonarcloud.io[/] to connect your GitHub account. Add the [blue]SONAR_TOKEN[/] secret, and the [blue]SONAR_ORGANIZATION[/] and [blue]SONAR_PROJECT_KEY[/] variables to the GitHub repository. The workflows are already configured for SonarCloud analysis.
0 commit comments