Reverse workaround for invalid template errors and apply fix #123
Conversation
This file contains 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.
Fixes #122
Description
Fix the issue with invalid templates by using inner scope variables and reverse the workaround from the PR# 117 and PR# 118.
Specific changes
template-with-new-rg.jsonwith the inner scope variable, declaration of the new variables in that scope, and used it.Note: when referring to all main YAML we are excluding the one for JS host to JS skill and with all the
template-with-new-rg.jsonwe are excluding the ones for the JS bots as this changes were already added in the PR# 121.Testing
All the pipelines were tested with these changes applied and were working properly.
