[artifacts] Push artifacts to mirrors defined in yaml config. #1498
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: We want to mirror our artifacts across multiple storage locations. Currently, each release script pushes to gcs in an adhoc fashion. This PR creates a new config file (
ci/artifact_mirrors.yaml
), which is a centralized definition of all of the places we'll store artifacts (excluding container images, which will have their own set of mirrors). This PR updates all the release scripts to parse this file, and push its artifacts to all of the mirrors defined in that file.Type of change: /kind cleanup
Test Plan: Tested by making RCs of each component (cloud, cli, operator, and vizier).