-
-
Notifications
You must be signed in to change notification settings - Fork 15
WIP: type/provider to manage secrets #94
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
base: master
Are you sure you want to change the base?
Conversation
1256c8c to
9c93346
Compare
729a3f7 to
91d1c75
Compare
94d59bf to
3cf9d5d
Compare
|
@traylenator could you have a look here please? |
bf84808 to
a2b88e2
Compare
…er, even if enabled
|
Had a play with this doing CRUD of secrets for Also with a deferred function e.g. quadlets_secret{'foobar:quiet':
secret => Deferred('oursecrets::get',['yoursecret']),
labels => {'foo' => 'bar'},
}I agree the title of Everything working really well. |
|
everything but these *#@!&.... acceptance tests ;( |
| commands podman: 'podman' | ||
|
|
||
| def should_user | ||
| @should_user || @should_user = resource[:name].split(':')[0] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we uninventing composite namevars here?
add type and provider to manage secrets.
Theoretically you can choose another driver than the default file, but I did not test that.