ci: enable docs deploy dispatch to docs.rockylinux.org - #3391
Merged
Conversation
Revives the disabled Fastly deploy trigger workflow: - event-type updated to deploy-docs (matches the S3 deploy workflow in rocky-linux/docs.rockylinux.org) - also triggers on rocky-8 and rocky-9 pushes (environment branch policy updated to allow these) - adds client-payload with repo/ref/sha for traceability The docs site now redeploys within ~20 minutes of a docs merge instead of waiting for the daily scheduled rebuild.
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
Revives the disabled
deploy.ymlworkflow so that merges to this repo immediately trigger a rebuild/deploy of docs.rockylinux.org, which now serves from S3 via Fastly (see rocky-linux/docs.rockylinux.org).Changes vs the old disabled file:
event-typeupdateddeploy-staging→deploy-docsto match the receiving workflow (build-docs.yml)rocky-8/rocky-9pushes; theproductionenvironment branch policy has been updated to allow these branchesclient-payload(repo/ref/sha) for traceability in the receiving runNotes
CROSS_REPO_PATenvironment secret (from Oct 2024). It will be validated with a manual run after merge and replaced with a fresh fine-grained PAT if it no longer works.vercel_main.yml) is untouched — dual publishing continues until Vercel is decommissioned.Test plan
workflow_dispatch)repository_dispatchrun starts in rocky-linux/docs.rockylinux.org and completeslast-modifiedrefreshes