sourceos: add artifact-truth scaffold for flavors, installer, channels, and manifests#9
Draft
sourceos: add artifact-truth scaffold for flavors, installer, channels, and manifests#9
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
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.
Summary
This PR adds the first bounded artifact-truth scaffold to
SourceOS.It complements the new
sociossubstrate automation scaffold by giving the substrate repo a reviewable place for:What lands
Boundary note
docs/ARTIFACT_TRUTH.mdDirectories and stubs
flavors/README.mdflavors/sourceos-workstation.example.yamlcosa/README.mdbutane/README.mdbutane/workstation/base.buinstaller/README.mdinstaller/live-usb-default.yamlinstaller/pxe-default.yamlchannels/README.mdchannels/dev.yamlmanifests/README.mdmanifests/release-manifest.example.jsonWhy here
SourceOSalready defines itself as the immutable substrate and explicitly says it is the substrate rather than the builder.That makes it the correct place to hold the definitions of what gets built and released, while leaving orchestration and provisioning automation to
socios.Important non-goals in this PR
This PR does not yet add:
Those belong downstream in
sociosor later follow-on tranches.Relationship to the broader effort
This PR is the substrate-side counterpart to:
workspace-inventorygraph expansionworkstation-contractsM2 IPC packsourceos-specshared content/build/release familysociosFCOS + Foreman/Katello substrate automation scaffoldTogether, those changes move the original build/provisioning goal out of chat and into the actual repo authorities.