-
Notifications
You must be signed in to change notification settings - Fork 4
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
chore: Version CRD and HbaseClusterConfig #624
base: main
Are you sure you want to change the base?
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.
LGTM, just a question and suggestion
pub authentication: Option<AuthenticationConfig>, | ||
|
||
#[serde(default, skip_serializing_if = "Option::is_none")] | ||
pub authorization: Option<AuthorizationConfig>, |
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 crd::security::AuthorizationConfig
not supposed to be versioned?
//! Ensures that `Pod`s are configured and running for each [`HbaseCluster`][v1alpha1] | ||
//! | ||
//! [v1alpha1]: crate::crd::v1alpha1::HbaseCluster |
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.
suggestion: specify the version in the docs 9to make it more obvious if the parameters change version.
//! Ensures that `Pod`s are configured and running for each [`HbaseCluster`][v1alpha1] | |
//! | |
//! [v1alpha1]: crate::crd::v1alpha1::HbaseCluster | |
//! Ensures that `Pod`s are configured and running for each [`v1alpha1::HbaseCluster`] |
Part of stackabletech/issues#642
This PR adds versioning to the HBase CRD and cluster config. It doesn't introduce any new version or updates the CRD in any way. It currently emits the same
crd.yaml
which is the correct expected behaviour.Tip
It is recommended to look at this PR on a commit-by-commit basis to better understand the individual steps taken. Also take a look at the macro documentation.