Skip to content

Commit

Permalink
chore: update accelerator release process (#663)
Browse files Browse the repository at this point in the history
  • Loading branch information
jaredfholgate authored Oct 18, 2023
1 parent abcd724 commit b5718e0
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/wiki/Contributing.md
Original file line number Diff line number Diff line change
Expand Up @@ -259,6 +259,6 @@ Each resource must use the latest available, working, API version. If the latest
### Release Process Diagram

When adding new parameters to a module, changing existing parameter names, or creating a new module, there are some additional steps that must be considered to ensure the [Accelerator](https://github.com/Azure/ALZ-Bicep/wiki/Accelerator) and the associated [ALZ-PowerShell-Module](https://github.com/Azure/Alz-powershell-module) remain in-sync. The following diagram outlines the steps for release process and provides additional context for changes that may be required:
When adding new parameters to a module, changing existing parameter names, or creating a new module, there are some additional steps that must be considered to ensure the [Accelerator](https://github.com/Azure/ALZ-Bicep/wiki/Accelerator) works with the associated [ALZ-PowerShell-Module](https://github.com/Azure/Alz-powershell-module). The accelerator publishes the [ALZ-Powershell.config.json](https://github.com/Azure/ALZ-Bicep/blob/main/accelerator/.config/ALZ-Powershell.config.json) file which contains the configuration required for accelerator deployment. The following diagram outlines the steps for release process and provides additional context for changes that may be required:

![Release Process](media/alz-bicep-release-process.png)
Binary file modified docs/wiki/media/alz-bicep-release-process.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit b5718e0

Please sign in to comment.