-
Notifications
You must be signed in to change notification settings - Fork 378
Clarify wording and naming of credentials in CSI #201
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
Clarify wording and naming of credentials in CSI #201
Conversation
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.
This LGTM!
csi.proto
Outdated
// An SP SHALL advertise the requirements for required secret keys and | ||
// values in documentation. | ||
// CO SHALL permit passing through the required secrets. CO MAY expose | ||
// secrets as a one or more map to its end users, therefore the keys |
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.
This wording is a bit funky to me.
What about something like this (assuming I'm understanding what's written):
A CO MAY send the same secrets to all RPCs, therefore the keys for all unique secrets that an SP expects must be unique across.
6610693
to
daf30c4
Compare
@cpuguy83 Reworded. PTAL |
daf30c4
to
43e03b6
Compare
43e03b6
to
f4418ed
Compare
Whoops fixed! |
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.
LGTM
Fixes #198
Alternate to #200
This PR: