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
bot account for shared credentials #615
Comments
|
I was going to add Should we have a separate, real email account we can use for this stuff (cloudflare superadmin, gandi, etc) and forward that to the admins as well? |
|
good idea 👍 |
|
Any preferences on which service to use? Might just use gmail? |
|
no preference |
|
I would just add a forwarding address mybotaccount@nix-community.org -> admin@community.org, and then use that to create the bot account. As long as we control the whole chain it's fine. |
I don't understand how using two aliases like this is different from using one alias? |
|
Yeah we need a domain that is not controlled by the registrar that we are trying to login to avoid dependency cycles. |
|
https://api.gandi.net/docs/authentication/ Gandi api keys are deprecated and have been replaced by personal access tokens. The terraform provider doesn't support tokens yet so I'll leave this until it does. |
|
I thought that we had another token linked to an admins account but I can't see one in the secrets. Closing as this seems it was only an issue with gandi. |
Currently some tokens are linked to admins accounts, e.g.
GANDI_KEY.The text was updated successfully, but these errors were encountered: