Skip to content

Conversation

heurtematte
Copy link
Contributor

@heurtematte heurtematte commented Sep 10, 2024

Renew GitLab API token for the bot user of the project <project_id> or all projects bots registered in the secretsmanager and all related tools: jenkins and otterdog (github org)

e.g:

Renew the token and update tools for the project technology.cbi:

  • gitlab_bot_token_renew.sh technology.cbi -f

Renew the token and update tools for all projects bots registered in the secretsmanager

  • gitlab_bot_token_renew.sh -f

Options:
-f: force regeneration of token
-t: keep token and force update on tools

@heurtematte heurtematte marked this pull request as draft September 10, 2024 15:49
@merks
Copy link

merks commented Sep 10, 2024

It's great to see preemptive action being take to improve token renewals in the future! ❤️ 🏆

@heurtematte heurtematte force-pushed the feat/gitlab_api_token_renew branch from a1ece31 to bc9cccd Compare September 11, 2024 14:42
@heurtematte heurtematte force-pushed the feat/gitlab_api_token_renew branch from bc9cccd to dee29b8 Compare September 16, 2024 07:41
@heurtematte heurtematte requested a review from fredg02 September 17, 2024 14:20
@heurtematte heurtematte marked this pull request as ready for review September 17, 2024 14:26
@fredg02
Copy link
Contributor

fredg02 commented Sep 20, 2024

I'm a bit confused why vault is being queried for the current token, but the renewed token is only stored in pass. 🤔

@heurtematte
Copy link
Contributor Author

Vault (secretsmanager) is only used to list the paths to the existing API token key, not for reading purposes.

This is more of a preparation for the transition to the secrets manager.

Signed-off-by: sebastien.heurtematte <[email protected]>
Copy link

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

Successfully merging this pull request may close these issues.

4 participants