Add CLI tool to manage stack image S3 bucket and manifests#392
Draft
Malax wants to merge 1 commit into
Draft
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.
Part of the Cheverny replacement, and the second of two chunks — the other one is #391, which covers the changelog and DevCenter package report generation. This PR covers the bucket and manifest management side.
Adds a suite of bash CLI tools under
bin/stacks-bucket/that manage the S3 bucket holding stack images and the signed manifest releases consumers resolve against. The tools cover uploading images, promoting them into a new manifest release, rolling back to a previous release, listing releases, and inspecting an individual manifest. Manifests are GPG-signed.The GHA glue that wires these up in CI will be added in a follow-up PR.