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.

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

Support externally defined providers #280

Open
vetsin opened this issue May 21, 2024 · 0 comments
Open

Support externally defined providers #280

vetsin opened this issue May 21, 2024 · 0 comments

Comments

@vetsin
Copy link

vetsin commented May 21, 2024

So that one may write custom providers of which are 'internal', a good example would be how docker does it:

So in teller world that may be:

providers:
  ecr-1: 
    kind: ecr-login

or more likely:

providers:
  ecr-1:
    kind: credential-helper
    bin: ecr-login

The idea being we use use stdin/out from other binaries as the interface, optionally.

Something like ProviderKind::CredentialHelper which literally just calls format!("teller-credential-{} {}", bin, action)? Albeit without the command injection

This may also allow fancier credential syncing where we may have needed a template before, e.g. if i wanted to setup a docker registry auth where our secret is an arbitrary provider, we may teller put it by essentially calling docker login ${registry:-} -u ${user} --password-stdin. I think before i would have needed docker-temp.t and then overloaded DOCKER_CONFIG locations, or some shell logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant