Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Improving Postgres CR Status with Additional Details #2714
base: master
Are you sure you want to change the base?
Improving Postgres CR Status with Additional Details #2714
Changes from 2 commits
d89e726
30ed723
0269432
061b051
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
why use an extra type and not just metav1.Time?
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.
Mostly to avoid semantic check inequality with
metav1.time
, with a wrapper aroundmetav1.time
there won't be a semantic inequality even if the times are different but everything else in the CR is same, this could be handy while writing unit tests or e2e tests I thinkThere 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.
@FxKu , Is this okay?
Check failure on line 212 in pkg/controller/postgresql.go
GitHub Actions / End-2-End tests
Check failure on line 212 in pkg/controller/postgresql.go
GitHub Actions / Unit tests and coverage
Check failure on line 215 in pkg/controller/postgresql.go
GitHub Actions / End-2-End tests
Check failure on line 215 in pkg/controller/postgresql.go
GitHub Actions / Unit tests and coverage