Repository navigation
Conversation
Lets POST /variable create an override of a higher-scope variable with the same key instead of returning 409. Also documents the 409 on createVariable.
Astach
approved these changes
Oct 22, 2026
This branch has not been deployed
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.
Jira: QOV-2445
Related changes:
Repo: qovery-openapi-spec
Adds an optional
override_if_existsboolean (nullable, default false) toVariableRequest, the body ofPOST /variable.Today, creating a variable whose key already exists at the project or environment scope returns 409, and the caller has to create an OVERRIDE variable separately. With
override_if_exists: true, the API creates the override instead. The usual override rules still apply: same secret kind, the target must be a value or file variable, and the new variable must sit at a strictly lower scope. The implementation lands in q-core.The
createVariabledescription now mentions the 409 and the flag, and the operation lists a409response, which q-core already returns but the spec did not declare.No breaking change: the field is optional and defaults to the current behavior.
Testing: spectral 6.5.1 with the built-in
spectral:oasruleset gives 0 errors and the same 244 warnings asmain.npm testcannot run because the Stoplight ruleset that.spectral.mjsimports returns 404.Summary by cubic
Adds an optional
override_if_existsflag toVariableRequestsoPOST /variablecan create an override of a higher-scope variable instead of returning 409.override_if_existsis true and a variable with the same key exists at a project or environment scope, the API creates the override rather than failing with 409; the usual override rules apply (same secret kind, value or file target, strictly lower scope).createVariabledescription and declares the409response in the spec; no breaking change since the field defaults to the current behavior.Written for commit 5bd95ab. Summary will update on new commits.