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

Refresh GHA Tugboat credentials #16734

Closed
1 of 5 tasks
Tracked by #16859
JunTaoLuo opened this issue Jan 8, 2024 · 10 comments
Closed
1 of 5 tasks
Tracked by #16859

Refresh GHA Tugboat credentials #16734

JunTaoLuo opened this issue Jan 8, 2024 · 10 comments
Assignees
Labels
DevOps CMS team practice area

Comments

@JunTaoLuo
Copy link
Contributor

JunTaoLuo commented Jan 8, 2024

User Story or Problem Statement

As a maintainer of the GHA infrastructure, the GHA credentials should not be owned by any one engineer but instead be managed centrally along with other secrets and credentials.

Description or Additional Context

This is a followup to the PRs #16562 and #16279. There are two credentials: TUGBOAT_API_TOKEN and LABEL_API_TOKEN. The current tokens are generated by me as a temporary measure but should be refreshed with a centrally managed account or DevOps like all other credentials.

Steps for Implementation

  • Refer to the Tugboat documentation for the required tokens and permissions required.
  • The tokens should be generated from a centrally managed account and updated in the Actions/Dependabot secrets environments

Acceptance Criteria

  • Tokens are refreshed and GHA Tugboat automation confirmed to be working as expected in this repo.

Team

  • CMS Team
  • Public Websites
  • Facilities
  • Accelerated Publishing
@JunTaoLuo JunTaoLuo added DevOps CMS team practice area Needs refining Issue status labels Jan 8, 2024
@JunTaoLuo
Copy link
Contributor Author

@maortiz-27-80 @BerniXiongA6 let's chat about this for the next refinement since one of the credentials has an expiry date. The task is simple but I'll need help from DevOps to figure out ownership.

@BerniXiongA6
Copy link

Hi @JunTaoLuo since we canceled backlog refinement, did you need to chat with @maortiz-27-80 and/me about this ticket? Let us know. Thanks!

@JunTaoLuo
Copy link
Contributor Author

Yup we should chat about this! The actual actions needed here are very quick but I just need to figure out who should own these credentials, thanks!

@BerniXiongA6
Copy link

OK @JunTaoLuo will grab time for @maortiz-27-80 you and me next week -- thank you!

@ndouglas
Copy link
Contributor

@JunTaoLuo you've onboarded with access for @va-cms-bot, right? It should own the credentials used here. If not, onboarding should be fairly painless. See here: #14345

@JunTaoLuo
Copy link
Contributor Author

Ah I don't think I ever onboard with that account. Would it be better for me to onboard with it now or work with someone who already has access?

@ndouglas
Copy link
Contributor

I can do it 🤷🏻 NBD

@ndouglas
Copy link
Contributor

This should be done now.

@JunTaoLuo
Copy link
Contributor Author

Thanks @ndouglas! I'll keep an eye out and see if everything works as expected when the workflows trigger.

@JunTaoLuo
Copy link
Contributor Author

Looks like everything is working thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DevOps CMS team practice area
Projects
None yet
Development

No branches or pull requests

3 participants