-
Notifications
You must be signed in to change notification settings - Fork 999
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
add to postgresql_type.go omitempty annotation #1223
Conversation
Looks similar to #1022 |
In fact it is similar to #1022. As I was still working with v.1.5.0, I had a lot more bugs until I switched to the current master branch. @FxKu Yes, I'll look at it again. It seems that more pointers would also be useful, because no structure values can be set on maps in Golang. However, I do not know if this would break compatibility. However, I will change it first. |
One thing that would most likely require a code change would be to solve the "not addressable" problem by using struct Pointers (instead of structs) https://stackoverflow.com/a/32751792 However, it only seems to be seriously needed in one case
|
using pointers for the PreparedDatabase structs sound like a story for another PR. I'm also not sure how easy it is to make this backwards compatible. |
I have removed the default value and resolved your review. |
Is the E2E test Flaky? I do not quite understand why the test should fail after this change. |
👍 |
👍 |
I use the PostgreSQL type to configure a struct instance in golang to create the resource in the k8s cluster.
To create the https://github.com/zalando/postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml in golang it is necessary to add some more
omitempty
annotations to unset values.Closes #1221