-
Notifications
You must be signed in to change notification settings - Fork 21
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
How to create "first api key" to use for any further authentication #188
Comments
Hi Florian, Thanks for getting in touch. Since
where:
I think the CLI and API are in good shape for this to be added in a point release without too many gotchas. What do you think? |
Hi Nick, sounds good. With this I would be able to create the initial token for further usage in other infra code. |
That sounds great, thanks Florian 👍 - it would be possible to set those values as environment variables as things are, but having them in values.yaml would be a big improvement for discoverability. |
Sent a PR to the other repo. |
Nick, if you give me some guidance on how to properly implement your ideas related to the new command line parameters for seqcli, I would be happy to contribute. |
Thanks Florian. I'm taking a look now, not 100% sure yet what is involved 👍 |
I started to sketch this out - it was a little tricky, I've pushed my progress in #190 - still needs some automated (and manual :-)) testing. Any eyes on that would be appreciated. |
Hi,
not sure I am missing something. I am currently trying to understand how I can setup a seq instance using infrastructure as code (pulumi in my case) and configure an initial api key with appropriate permissions that can then be used by seqcli. Consider the following flow of things:
After thinking of it for a few minutes, the best idea I have right now is to deploy such an "admin" credential together with the helm chart. Such a credential could then be easily used by down-stream projects using whatever credential management you want to use (vault, pulumi secrets, ...).
The text was updated successfully, but these errors were encountered: