Add a GCS deploy workflow #45
Merged
Commits on Mar 4, 2024
-
This uploads the repository to GCS and invalidates the CDN cache. * the workflow is a custom one for root-signing * it is called as a reusable workflow from the TUF-on-CI publish workflow (so gets automated issue failing on errors) GCP configuration is mostly hard coded, only service accunt details are inputs: * service account: same as online signing * project: projectsigstore-staging * GCS bucket: tuf-root-staging * CDN load balancer: tuf-repo-cdn-lb Signed-off-by: Jussi Kukkonen <[email protected]>
-
workflows: Add missing arguments to deploy-to-gcs
Signed-off-by: Jussi Kukkonen <[email protected]>
-
deploy-to-gcs: Use gcloud storage rsync
rsync features: * exclude list (used for timestamp) * --delete-unmatched-destination-objects may be useful in future to delete unused metadata files Note that gcloud rsync CLI is not the same as unix rsync: the SOURCE and DEST arguments in particular function completely differently. Also put some variables into actual named variables. Signed-off-by: Jussi Kukkonen <[email protected]>
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.