-
Notifications
You must be signed in to change notification settings - Fork 64
K8SPG-748 update statuses #1220
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
base: main
Are you sure you want to change the base?
Conversation
@@ -2,7 +2,6 @@ package pgcluster | |||
|
|||
import ( | |||
"context" | |||
|
|||
"github.com/pkg/errors" |
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.
[goimports-reviser] reported by reviewdog 🐶
"github.com/pkg/errors" | |
"github.com/pkg/errors" |
…ostgresql-operator into K8SPG-748_add_statuses
commit: 6667b96 |
@@ -443,7 +443,11 @@ type PerconaPGClusterStatus struct { | |||
|
|||
// +optional | |||
// +operator-sdk:csv:customresourcedefinitions:type=status | |||
PatroniVersion string `json:"patroniVersion"` | |||
PatroniStatus PatroniStatus `json:"patroniStatus,omitempty"` |
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.
So this will look like this
Patroni Status:
Patroni:
System Identifier: 7528392001833009250
Patroni Version: 4.0.5
There is a lot of repetition of the reference to Patroni, making the status very verbose.
I think we should have something like that:
Patroni:
Status:
System Identifier: 7528392001833009250
Version: 4.0.5
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.
@egegunes what do you think? if you ok, I will rename it.
CHANGE DESCRIPTION
Problem:
we need to synchronize statuses from postgres cluster to percona cluster
Cause:
Short explanation of the root cause of the issue if applicable.
Solution:
Short explanation of the solution we are providing with this PR.
CHECKLIST
Jira
Needs Doc
) and QA (Needs QA
)?Tests
Config/Logging/Testability