-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: add release channel support for pulsar cluster #44
Conversation
Signed-off-by: lili <[email protected]>
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.
Please run go generate ./...
for update docs
Signed-off-by: lili <[email protected]>
"release_channel": { | ||
Type: schema.TypeString, | ||
Optional: true, | ||
Default: "rapid", |
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.
Is the rapid channel used by default?
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.
yes, on UI also uses the rapid as default
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.
yes, keep consistent with console UI
cloud/resource_pulsar_cluster.go
Outdated
Optional: true, | ||
Default: "rapid", | ||
Description: descriptions["release_channel"], | ||
ValidateFunc: validateNotBlank, |
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.
Maybe you can add a function validateReleaseChannel
to verify if it is lts, rapid or null.
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.
fixed, thanks.
Signed-off-by: lili <[email protected]>
Signed-off-by: lili <[email protected]>
done, thanks. |
Signed-off-by: lili <[email protected]>
Signed-off-by: lili <[email protected]>
Signed-off-by: lili <[email protected]>
Signed-off-by: lili <[email protected]>
fix #43