Open
Conversation
Use the upgrade command to auto-deploy new cloud shell image configuration on new version publish
Contributor
|
This seems like it could have serious security implications so I think we should look at it more closely. |
Member
Author
|
It only is triggered on new releases being published at the moment, and just automates the config update to use the new image tag |
floreks
approved these changes
Aug 21, 2023
maciaszczykm
approved these changes
Aug 22, 2023
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
4 participants
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.
Summary
Use the upgrade command to auto-deploy new cloud shell image configuration on new version publish
Test Plan
tested the envsubst command locally
Checklist