Skip to content

include status subresource in validation #744

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

Merged
merged 2 commits into from
Dec 2, 2019
Merged

include status subresource in validation #744

merged 2 commits into from
Dec 2, 2019

Conversation

FxKu
Copy link
Member

@FxKu FxKu commented Nov 30, 2019

otherwise editing manifests is a bit tedious.

EDIT: When running Postgres clusters since before the v1.2.0 release, it could be that the status is still in the old format, which is Status: string. This happens because during sync we only update the status to the new format, if the status was not running. The validation does not affect running clusters. When you create new ones, you will not specify the status as this is up to the operator to define. You would only run into an error when manually editing the manifest, with status not being PostgresClusterStatus: Running. But then you would simply delete that line, and validation would succeed. That's actually the scenario this PR want's to solve for the new format 😃

@sdudoladov
Copy link
Member

@FxKu for documentation purposes please add a comment describing why this validation should not affect older postgresql manifests where the status was a string and not a subresource

@sdudoladov
Copy link
Member

👍

1 similar comment
@FxKu
Copy link
Member Author

FxKu commented Dec 2, 2019

👍

@FxKu FxKu merged commit 11c2e81 into master Dec 2, 2019
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.

3 participants