scope_definition: optional package registration (spec+actions+artifacts BOM)#446
Open
sebasnallar wants to merge 1 commit into
Open
scope_definition: optional package registration (spec+actions+artifacts BOM)#446sebasnallar wants to merge 1 commit into
sebasnallar wants to merge 1 commit into
Conversation
…tions + artifacts) var.package publishes the definition as a versioned package: components pin the service specification and every action specification at their latest snapshots (automatic), plus caller artifacts — created inline (meta), resolved by identity lookup (no ids in config), or pinned by explicit ids. Verified end-to-end against the real API: create from zero, identity lookup, version bump publishing a second revision with default promotion, destroy.
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.
Adds an opt-in
packagevariable tonullplatform/scope_definition: when set, the module publishes the definition as a versioned package whose bill of materials pins the service specification + every action specification (snapshotted automatically via the provider'slast_snapshot_id) + caller-supplied artifacts.Artifacts support three modes per entry:
metagiven: registers a new artifact revision inlinelookup = true+ identitymeta(registry+repository…): resolves an artifact registered elsewhere (CI /np package publish) — no ids in configuration; latest revision unless digest/reference pins oneresource_id+resource_revision_idVerified end-to-end against the real API with a locally-built provider (branch
feat/packages-artifacts-resources): from-zero apply (20 resources), identity lookup, version bump 0.0.1→0.0.2 publishing a second revision + default promotion, full destroy.examples/package/is the applied configuration.Reviewer notes:
tagsadditionally needs the API's release-tag routes.DELETE /packages/:idleaks component claims; re-publishing an existing version replaces its revision (no BOM-mismatch guard within the same package).