[CI Environment] Enable 'Publish if not exists' + Fix for 'Publish latest'#2410
Merged
AlexanderSehr merged 40 commits intomainfrom Dec 23, 2022
Merged
[CI Environment] Enable 'Publish if not exists' + Fix for 'Publish latest'#2410AlexanderSehr merged 40 commits intomainfrom
AlexanderSehr merged 40 commits intomainfrom
Conversation
eriqua
reviewed
Dec 7, 2022
eriqua
reviewed
Dec 7, 2022
docs/wiki/Getting started - Scenario 2 Onboard module library and CI environment.md
Outdated
Show resolved
Hide resolved
eriqua
reviewed
Dec 7, 2022
Co-authored-by: Erika Gressi <56914614+eriqua@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
In case people onboard CARML directly into main they have to apply workarounds to get their modules to publish as the CI envrionment expects a merge to main with module changes in order to publish.
This PR mitigates this issue but not only searching for changes, but also checking of any given module (or child-module) is already part of the target environment (e.g. Bicep Registry, Template Specs, Azure DevOps Artifacts Feed).
Also, this PR fixes an issue with the 'Publish latest' in that it adds a missing passthru of the settings.yml variable to the actual function that needs it.
Required tests:
The idea for a 'first' run in an 'empty' environment is to see an output such as
Bicep registry example
Then, for any subsequent run, the output should look similar to
Bicep registry example
Type of Change
Please delete options that are not relevant.
Checklist