fix(legacy): forward --level from variable:create --update to variable:update - #200
Closed
pjcdawkins wants to merge 1 commit into
Closed
pjcdawkins wants to merge 1 commit into
pjcdawkins wants to merge 1 commit into
Conversation
…e:update When the variable already existed and --update was set, variable:create ran variable:update without --level. If the name existed at both the project and environment levels, variable:update then failed with "Variable found at both project and environment levels", even though --level had been passed. Forward the requested level to the sub-command, and add an integration test that updates a name existing at both levels via each level. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #199, which makes the same fix and also covers |
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
1 participant
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.
When a variable already existed and
--updatewas set,variable:createranvariable:updatewithout--level. If the name existed at both the project and environment levels, the update failed with "Variable found at both project and environment levels", even though--levelhad been passed.The requested level is now forwarded to the sub-command.
variable:updatealready handles--level, so it is unchanged. The Go wrapper has novariable:*code path.Adds an integration test that updates a name existing at both levels, once with
--level environmentand once with--level project.🤖 Generated with Claude Code