Motivation
I'm planning to set up this action for my Elixir project, and noticed that the Action's instructions make it seem like the Action only takes the Gigalixir username and password.
Gigalixir also supports an API key for interaction with the API it seems, that I think might be a better option, as it would let you supply just an API token that may be revoked, instead of what seems like the login credentials for the whole Gigalixir account.
Is it possible currently to use the API key (as another Action Secret), or if not, how difficult would it be to add support to the Action?
I saw some more information about the API key can here:
https://buildmedia.readthedocs.org/media/pdf/gigalixir/latest/gigalixir.pdf
21.5 Authentication When you login with your email and password, you receive an API key. This API key is stored in your ~/.netrc file. Commands generally use your ~/.netrc file to authenticate with few exceptions.
Motivation
I'm planning to set up this action for my Elixir project, and noticed that the Action's instructions make it seem like the Action only takes the Gigalixir username and password.
Gigalixir also supports an API key for interaction with the API it seems, that I think might be a better option, as it would let you supply just an API token that may be revoked, instead of what seems like the login credentials for the whole Gigalixir account.
Is it possible currently to use the API key (as another Action Secret), or if not, how difficult would it be to add support to the Action?
I saw some more information about the API key can here:
https://buildmedia.readthedocs.org/media/pdf/gigalixir/latest/gigalixir.pdf
21.5 Authentication When you login with your email and password, you receive an API key. This API key is stored in your ~/.netrc file. Commands generally use your ~/.netrc file to authenticate with few exceptions.