Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Actions to Properly Use PAT for Website Build and Deployment (#1726) #1731

Conversation

aj-stein-nist
Copy link
Contributor

@aj-stein-nist aj-stein-nist commented Mar 31, 2023

Committer Notes

Update PAT configuration for builds, monitor rate limiting, and disable per commit link checking for PRs. Closes #1698 and #1726.

All Submissions:

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

Changes to Core Features:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you included examples of how to use your new feature(s)?
  • Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.

@aj-stein-nist aj-stein-nist self-assigned this Mar 31, 2023
@aj-stein-nist aj-stein-nist linked an issue Mar 31, 2023 that may be closed by this pull request
@aj-stein-nist aj-stein-nist changed the title 1726 pat permissions issues for cd auto commit for docs pages Update Actions to Properly Use PAT for Website Build and Deployment (#1726) Mar 31, 2023
By doing this, we correctly the PAT usage and not ironically use an existing,
but improperly permissioned GITHUB_TOKEN provided as a context machine identity
for all runs of all workflows, this should fix the builds and stop the cryptic
HTTP 429 rate limit error response. It's cryptic because you get a 429 response
after one single API operation (with git clone) because the token is wrong.
As part of the troubleshooting work, GH docs do indicate scanning links from the GHA
runners can potentially cause rate limiting. We have automated nightly scans and we
review code changes as part of PRs. We can forgot commit-by-commit link scanning as
a short-to-medium term mitigation and enable it again later.
@aj-stein-nist aj-stein-nist force-pushed the 1726-pat-permissions-issues-for-cd-auto-commit-for-docs-pages branch from abaea76 to 610c5da Compare March 31, 2023 21:22
Copy link
Contributor

@nikitawootten-nist nikitawootten-nist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks straightforward. LGTM.

@aj-stein-nist aj-stein-nist merged commit e8f09a9 into main Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants