-
Notifications
You must be signed in to change notification settings - Fork 387
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
[Improvement] Make property cloud.name
and cloud.region-code
mutable
#4999
Comments
Hi @mchades , I want to follow up this issue. Can it be assigned to me? Best Regards, |
Sure, assigned. @LindaSummer |
Hi @mchades , Sorry to bother you. I'm not sure related test case should be put in which test class. Could you give me some advice? Best Regards, |
You can modify the tests: Lines 105 to 106 in a89fe92
and add integration tests to here: Line 45 in a89fe92
|
…ble. (#5025) ### What changes were proposed in this pull request? Make catalog property `cloud.name` and `cloud.region-code` mutable. ### Why are the changes needed? As #4999 mentioned, the `cloud.name` and `cloud.region-code` may change after first creation. Fix: #4999 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Related integration tests have been added in this PR.
What would you like to be improved?
Because there is a possibility that the creation was filled in incorrectly, or that the region changed as the URL of the catalog changed, we should allow modification of these two properties
How should we improve?
Make property
cloud.name
andcloud.region-code
mutableThe text was updated successfully, but these errors were encountered: