You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow credentials to be passed to the provider without storing those on the local machine
Describe the Solution You Would Like
vault_secret_engine { 'nomad':
type => 'nomad',
ensure => 'present',
description => 'dynamic token management for nomad',
vault_token => 'my super token',
}
Writing providers like this one for vault or even the consul one (https://github.com/solarkennedy/puppet-consul/blob/master/lib/puppet/provider/consul_policy/default.rb) some times require different tokens for each type of operation, the issue is that you don't have access to attributes during get or prefetch and it leads to hacks to make it work. I'd like have access to specific values so it become possible to use these values on API requests without the need to a transport.
The text was updated successfully, but these errors were encountered:
There's a prototype implementation for this in #284 (for #242) - the missing piece there is verifying that the implementation doesn't leak the catalog across agent runs.
Use Case
Allow credentials to be passed to the provider without storing those on the local machine
Describe the Solution You Would Like
Writing providers like this one for vault or even the consul one (https://github.com/solarkennedy/puppet-consul/blob/master/lib/puppet/provider/consul_policy/default.rb) some times require different tokens for each type of operation, the issue is that you don't have access to attributes during get or prefetch and it leads to hacks to make it work. I'd like have access to specific values so it become possible to use these values on API requests without the need to a transport.
The text was updated successfully, but these errors were encountered: