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.

Sign up for GitHub

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

Jump to bottom

Add information about GitHub/GitLab token changes after cluster creation #625

Closed
1 task done
fharper opened this issue Jan 8, 2024 · 1 comment
Closed
1 task done

Add information about GitHub/GitLab token changes after cluster creation #625

fharper opened this issue Jan 8, 2024 · 1 comment
Labels
duplicate This issue already exists

Comments

@fharper
Copy link
Member

fharper commented Jan 8, 2024

What type of suggestions?

Missing Information

What page is concerned?

FAQ

What version of the docs?

2.3+

What is the issue?

We need to write about what is happening if you need to recreate or change the GitHub or GitLab token after you created a Kubernetes cluster with kubefirst. It's something that can surely happen for security reason, or with the new GitHub token (don't know if GitLab has the same mechanesism) that expired after a set amount of time.

tl;dr

The user need to update the token for Atlantis in Vault, and everything should continue to work together.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@fharper fharper added the duplicate This issue already exists label May 13, 2024
@fharper
Copy link
Member Author

fharper commented May 13, 2024

duplicate of #698

@fharper fharper closed this as not planned Won't fix, can't repro, duplicate, stale May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate This issue already exists
Projects
Kubefirst Action
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fharper