VCST-5063: Add optional appInsightsInstrumentationKey input#53
Merged
Conversation
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.
Note
Medium Risk
Touches shared GitHub Actions workflows used across many repos by bumping the referenced template version and adding an optional secret, which could impact CI runs if misconfigured, but does not change application/runtime code.
Overview
Updates the reusable GitHub Actions workflow set to
v3.800.35(and updates module template references/defaults accordingly).Extends the
pytest-tests.ymlreusable workflow with an optionalappInsightsInstrumentationKeysecret and forwards it intodocker-env-full, and wires module CI templates to passE2E_APPINSIGHTSINSTRUMENTATIONKEYthrough when running auto-tests.Reviewed by Cursor Bugbot for commit 79d74ec. Bugbot is set up for automated code reviews on this repo. Configure here.