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.

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

chore: remove un-required version number and tidy docs #685

Merged
merged 1 commit into from
Nov 16, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion accelerator/.config/ALZ-Powershell.config.json
Original file line number Diff line number Diff line change
Expand Up @@ -512,7 +512,7 @@
},
"UpstreamReleaseVersion": {
"Type": "Computed",
"Value": "v0.16.6",
"Value": "{REPLACED_BY_ALZ_POWERSHELL_MODULE}",
"Targets": [
{
"Name": "UPSTREAM_RELEASE_VERSION",
Expand Down
4 changes: 2 additions & 2 deletions docs/wiki/Accelerator.md
Original file line number Diff line number Diff line change
Expand Up @@ -219,7 +219,7 @@ With the ALZ Accelerator framework, we have designed the pipelines and directory

1. Using the ALZ PowerShell Module, there is a cmdlet called `Get-ALZBicepRelease`. This will download a specified release version from the remote ALZ-Bicep repository and pull down to the local directory where your Accelerator framework was initially deployed.

Here is an example of using the cmdlet to pull down version v0.16.5:
Here is an example of using the cmdlet to pull down version v0.16.6:

```powershell
Get-ALZGithubRelease -githubRepoUrl "https://github.com/Azure/ALZ-Bicep" -release "v0.16.6" -directoryForReleases "C:\Repos\ALZ\accelerator\upstream-releases\"
Expand All @@ -228,7 +228,7 @@ With the ALZ Accelerator framework, we have designed the pipelines and directory
1. Once the ALZ Bicep release has been downloaded, you will need to update `upstream-releases-version` within the environment variables file (.env) with the version number of the release that you just downloaded. For example, if you downloaded v0.16.5, you would update the file with the following:

```text
UPSTREAM_RELEASE_VERSION="v0.16.5"
UPSTREAM_RELEASE_VERSION="v0.16.6"
```

1. You can now deploy the updated modules.
Expand Down
Loading