Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional Accelerator upgrade guidance #708

Merged
merged 3 commits into from
Dec 30, 2023
Merged

Additional Accelerator upgrade guidance #708

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
feb78bb
Upgrade guidance added
stalejohnsen Dec 22, 2023
eac6862
Fix trailing whitespace
stalejohnsen Dec 22, 2023
6c1c25d
fix code language
stalejohnsen Dec 22, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docs/wiki/Accelerator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,8 +228,15 @@ With the ALZ Accelerator framework, we have designed the pipelines and directory
```powershell
Get-ALZGithubRelease -i "bicep" -v "v0.17.0" -o "C:\Repos\ALZ\accelerator"
```

Verify that the cmdlet has updated the environment variables file (.env):
```bash
UPSTREAM_RELEASE_VERSION="v0.17.0"
```
1. You can now deploy the updated modules.
> **Note:**
> The current pipelines trigger What-If deployment in PRs for changes in the Bicep parameter files. If you also want to include the What-If deployment process in the module upgrade process, consider the following options:
> - Adding the environment variables file (.env) as an additional trigger in the module pipelines
> - Introducing inputs/parameters in the module pipelines so you can manually trigger What-If deployments in a controlled manner.

### Incorporating Modified ALZ Modules

Expand Down
Loading