Infra Update: New Release Provenance Database and Workflow Triggers#105
Merged
Infra Update: New Release Provenance Database and Workflow Triggers#105
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
2 participants
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.
References issue ACCESS-NRI/build-cd#263 and PR ACCESS-NRI/build-cd#269
References issue ACCESS-NRI/build-cd#238
Important
This PR is a major update to the deployment infrastructure. See below for the prerequisites for this repository to be able to merge this PR.
Background
This Infrastructure update moves away from the old build database at https://experiment-metadb-seven.vercel.app/release-provenance to a more modern database as part of
ACCESS-NRI/tracking_services, at https://reporting-dev.access-nri-store.cloud.edu.au/release-provenance/releases.We also allow rebuilding of prereleases
on.pull_request.types.ready_for_reviewandon.pull_request.types.converted_to_draft, which removes a small but significant loophole in which someone works on a draft PR (with less restrictivespack.yamlchecks) and then converts it to Ready For Review.Prerequisites for Merging
build-cdentrypoints (this PR!)secrets.BUILD_DB_CONNECTION_STR(from the old build database)* Release) Variablevars.TRACKING_SERVICES_POST_URL(URL for posting release data)* Release) Secretsecrets.TRACKING_SERVICES_POST_TOKEN(Token for posting release data)