Repository navigation
feat: expose metadata-only project environment resolution - #153
Merged
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.
Planning code needs environment key names, winning scopes and secret flags without loading decryption keys or exposing stored values.
resolveProjectEnvMetadatanow provides that metadata through the existing project-env owner. The runtime resolver shares the extracted target-scope projection, preserving layer precedence, tombstones, host/service collisions and unknown-scope behavior.The new API returns only selection/file paths, scope names and per-target metadata; it never returns plaintext, ciphertext or raw/merged layers. Missing modern configuration remains
nullfor callers to handle their existing legacy fallback. Metadata reads refuse failed reads, dangling links and non-file inputs with a value-free error; existing runtime reads and diagnostics retain their behavior. Readable symlinks remain supported.Validation:
Release signal:
featfor a repository API; no CLI interface or execution behavior change. This is a prerequisite for metadata planning, not a completed native configuration compiler. Paths and names remain private project metadata; the API is not portable plan serialization or an atomic input/admission fence, and does not prove encrypted values can be decrypted.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.