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

Rethink the DX of secrets/config #2385

Open
alecthomas opened this issue Aug 15, 2024 · 0 comments
Open

Rethink the DX of secrets/config #2385

alecthomas opened this issue Aug 15, 2024 · 0 comments
Assignees
@alecthomas
Labels
dx

Comments

@alecthomas
Copy link
Collaborator

Problems:

  • Knowing which cluster uses what secret backend - 1Password, AWS, ...?
    Don't allow separate backends per cluster - have a single backend that is configured at cluster creation. eg. locally it might be 1Password, in prod AWS, etc.
  • Setting the same secret across all clusters is confusing/difficult:
    Suggestion from @mistermoe: once we have profiles the FTL CLI could prompt you to set the same secret in every profile
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alecthomas alecthomas

Labels
dx
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alecthomas