Skip to content

spec: Clarify Plugin Name Rules #149

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

Merged

Conversation

edisonxiang
Copy link
Contributor

The plugin name will be passed in through CO's
APIs by the users to refer to the plugin.
CSI should clarify the plugin name rules.
This patch sepecifies the name in Reverse domain
name notation format.

Resolves: #145, #3

The plugin name will be passed in through CO's
APIs by the users to refer to the plugin.
CSI should clarify the plugin name rules.
This patch sepecifies the name in Reverse domain
name notation format.

Resolves: container-storage-interface#145, container-storage-interface#3
Copy link
Member

@jieyu jieyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM!

Copy link
Member

@saad-ali saad-ali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @edisonxiang for the PR!!

Minor change in wording otherwise LGTM

csi.proto Outdated
@@ -82,7 +82,13 @@ message GetPluginInfoRequest {
}

message GetPluginInfoResponse {
// This field is REQUIRED.
// Specify the name in Reverse domain name notation format,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would change the wording slightly:

The name MUST follow reverse domain name notation format (https://en.wikipedia.org/wiki/Reverse_domain_name_notation). It SHOULD include the plugin's host company name and the plugin name, to minimize the possibility of collisions. It MUST be 63 characters or less, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), underscores (_), dots (.), and alphanumerics between. This field is REQUIRED.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, Thanks for your suggestion.

@saad-ali
Copy link
Member

LGTM!

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

Successfully merging this pull request may close these issues.

4 participants