Skip to content
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(mongodb): add support for v1alpha1 #2777

Merged
merged 28 commits into from
Oct 28, 2024
Merged

Conversation

jremy42
Copy link
Contributor

@jremy42 jremy42 commented Oct 17, 2024

No description provided.

@jremy42 jremy42 changed the title Feat/add support for mondo db Feat/add support for mondodb Oct 17, 2024
@jremy42 jremy42 force-pushed the feat/add_support_for_mondoDB branch from 4bed7e2 to 22c5348 Compare October 17, 2024 10:13
@jremy42 jremy42 marked this pull request as ready for review October 17, 2024 11:47
@jremy42 jremy42 requested a review from remyleone as a code owner October 17, 2024 11:47
@remyleone remyleone changed the title Feat/add support for mondodb Feat/add support for mongodb Oct 17, 2024
@remyleone remyleone changed the title Feat/add support for mongodb feat(mongodb): add support for v1alpha1 Oct 17, 2024
@jremy42 jremy42 changed the title feat(mongodb): add support for v1alpha1 Draft: feat(mongodb): add support for v1alpha1 Oct 17, 2024
@jremy42 jremy42 changed the title Draft: feat(mongodb): add support for v1alpha1 feat(mongodb): add support for v1alpha1 Oct 17, 2024
@jremy42 jremy42 force-pushed the feat/add_support_for_mondoDB branch 4 times, most recently from e118e28 to ce3f07c Compare October 22, 2024 08:12
"user_name": {
Type: schema.TypeString,
Optional: true,
ForceNew: true,
Copy link
Member

Choose a reason for hiding this comment

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

Does that mean that changing the name of a user_name will imply the recreation of the whole instance?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, the user_name cannot be updated at the moment, so changing it will indeed trigger the recreation of the whole instance.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

doing nothing be a better solution?

Copy link
Member

Choose a reason for hiding this comment

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

Maybe having a dedicated resource for user, it is early but I would feel more comfortable with that rather than having a forcenew that could have large consequences if handled badly

},
},
"node_number": {
Type: schema.TypeInt,
Copy link
Member

Choose a reason for hiding this comment

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

It should be non zero

updateUserRequest.Password = &password
}

if updateUserRequest.Password != nil {
Copy link
Member

Choose a reason for hiding this comment

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

Same here, introduce a variable and check this variable to ensure than an update should be performed

@jremy42 jremy42 force-pushed the feat/add_support_for_mondoDB branch from 8e36460 to fe47373 Compare October 23, 2024 13:41
@remyleone remyleone added this pull request to the merge queue Oct 28, 2024
Merged via the queue into master with commit 5817807 Oct 28, 2024
46 checks passed
@remyleone remyleone deleted the feat/add_support_for_mondoDB branch October 28, 2024 15:47
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.

2 participants