fedora-infrastructure

#7213 Add Github access token to private secrets for release-monitoring.org and stg.release-monitoring.org
Closed: Fixed Opened by zlopez.

Closed: Fixed
Reopen Issue
  • Describe what you need us to do:
  • Generate GitHub access token https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/ (with only repo:status and public_repo scopes)
  • Add it to ansible secrets to be accessible from release-monitoring Ansible script

There should be two access tokens (staging and production).

  • When do you need this? (YYYY/MM/DD)
    As soon as possible.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    N/A

  • If we cannot complete your request, what is the impact?
    GitHub API will not work when new version of Anitya is deployed.

Metadata Update from @smooge:
- Issue assigned to smooge

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

I have created two tokens for the fedorainfra user and added them to ansible_private with the variable names:

github_prod_release_monitoring
github_stg_release_monitoring

Metadata Update from @smooge:
- Issue priority set to: Needs Review (was: Waiting on Assignee)

Closing ticket for time being. :scream_cat:

Metadata Update from @smooge:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.