feat: add cds config command for persisted project defaults - #537
Open
RonaldHensbergen wants to merge 1 commit into
Open
feat: add cds config command for persisted project defaults#537RonaldHensbergen wants to merge 1 commit into
RonaldHensbergen wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
Implements #383: a
cds configsubcommand family to manage persisted project-level defaults in.cds/config.json(orCDS_CONFIG_PATH), generalizing the existing single-purposecds usecommand.cds config get <key>/set <key> <value>/unset <key>/listprofile,environment,security.strictcds config set environment <name>validates the overlay exists for the configured default profile (reusingresolve_profile), mirroring the existingcds useprofile validationcds config set security.strict trueforces the production security rule class (infer_profile_classoverride) regardless of the profile's declared environmentenvironmentdefault is applied whenever--environmentis omitted, for all commands that already accept--environment(validate,plan,render,up,test,preflight,init,security); an explicit--environmentflag always takes precedence, and rendering a saved Plan file still rejects an explicit--environment(a config-derived default is silently ignored there, since the overlay was already baked into the plan)cds useis unchanged / kept as the profile-only convenience command; both now share_read_config/_write_configTesting
python -m unittest discover -s tests -p "test_*.py" -v— 561 tests, all passmake lint— passesResolves #383