-
Notifications
You must be signed in to change notification settings - Fork 4
ivorysql opertor V4 release #79
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,7 +13,7 @@ bases: | |
| images: | ||
| - name: ivory-operator | ||
| newName: docker.io/ivorysql/ivory-operator | ||
| newTag: v1.1 | ||
| newTag: v4.0 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Verification agent 🧩 Analysis chainOperator image updated to v4.0 release. The image tag has been properly updated to reflect the new IvorySQL Operator v4.0 release. This major version increment aligns with the PR objectives for the V4 release. Verify that the v4.0 image tag exists and is available: 🏁 Script executed: #!/bin/bash
# Verify the availability of the v4.0 image tag
docker pull docker.io/ivorysql/ivory-operator:v4.0 2>/dev/null && echo "Image v4.0 exists" || echo "Image v4.0 not found"Length of output: 103 IvorySQL Operator image tag v4.0 not found The kustomization is referencing a nonexistent operator image tag. Please ensure that • File: newTag: v4.0🤖 Prompt for AI Agents |
||
|
|
||
| patchesJson6902: | ||
| - target: { group: apps, version: v1, kind: Deployment, name: ivyo } | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -106,7 +106,7 @@ func (r *Reconciler) handlePatroniRestarts( | |
| return r.PodExec(pod.Namespace, pod.Name, container, stdin, stdout, stderr, command...) | ||
| }) | ||
|
|
||
| return errors.WithStack(exec.RestartPendingMembers(ctx, "master", naming.PatroniScope(cluster))) | ||
| return errors.WithStack(exec.RestartPendingMembers(ctx, "primary", naming.PatroniScope(cluster))) | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Verification agent 🧩 Analysis chainLGTM! Role terminology standardization to "primary". The change from "master" to "primary" aligns with modern inclusive terminology standards. Ensure that all role-dependent components (Patroni, instance recognition logic, etc.) consistently use the "primary" designation. Verify that role recognition is consistent across the codebase: 🏁 Script executed: #!/bin/bash
# Description: Verify consistent role terminology usage across the codebase.
# Search for any remaining "master" role references that might need updating
echo "=== Checking for remaining 'master' role references ==="
rg -i 'role.*master|master.*role' --type go --type yaml
echo "=== Verifying 'primary' role usage ==="
rg -i 'role.*primary|primary.*role' --type go --type yaml
echo "=== Checking RestartPendingMembers function signature ==="
ast-grep --pattern 'func $_ RestartPendingMembers($$$) $$$'Length of output: 8665 Ensure Complete Migration from “master” to “primary” A repository-wide search shows numerous remaining references to the old “master” role in both code and tests. To avoid inconsistencies at runtime and in your CI tests, please update every occurrence to the new • internal/naming/labels.go A global search-and-replace (e.g. 🤖 Prompt for AI Agents |
||
| } | ||
|
|
||
| // When the primary does not need to restart but a replica does, restart all | ||
|
|
||
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.
💡 Verification agent
🧩 Analysis chain
LGTM! Version pinning improves CI reproducibility.
Pinning the golangci-lint-action to a specific version (v1.60.1) instead of using "latest" is a best practice that ensures reproducible builds and prevents unexpected CI failures from breaking changes in newer versions.
Let me verify that this version exists and is valid:
🏁 Script executed:
Length of output: 130
Let’s recheck the release tag using a direct GitHub API call:
🏁 Script executed:
Length of output: 208
Invalid golangci-lint-action version pin – v1.60.1 not found
The GitHub API returned HTTP 404 for
releases/tags/v1.60.1, so CI will break trying to fetch a non-existent release. Please update the version on line 55 of.github/workflows/lint.yamlto a valid tag (see https://github.com/golangci/golangci-lint-action/releases):• File:
.github/workflows/lint.yamlLine 55:
📝 Committable suggestion
🤖 Prompt for AI Agents