Skip to content
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

chore: update application-api version #489

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

14rcole
Copy link
Collaborator

@14rcole 14rcole commented Oct 31, 2024

What does this PR do?:

The component status CRD had a new field to it, but application-service would overwrite the field when anyone attempted to update it. Updating application-service to the newest version of application-api fixes this issue

Which issue(s)/story(ies) does this PR fixes:

There isn't a story for this, but it unblocks an issue that will allow us to implement STONEINTG-1008

PR acceptance criteria:

  • Unit/Functional tests

  • Documentation

  • Client Impact

How to test changes / Special notes to the reviewer:

Deploy the change to a cluster. Create a component on the cluster and patch it with kubectl patch component --type json ${COMPONENT_NAME} -p '{"status": {"lastPromotedImage": "quay.io/test/sample-image:latest"}}' --type merge --subresource status --dry-run=server -o yaml. Without this change the yaml output will not show .status.lastPromotedImage. With this change it will.

@14rcole
Copy link
Collaborator Author

14rcole commented Nov 1, 2024

Check Format failed due to an invalid go version in the goimports go.mod but I can't reproduce the issue. Retriggering in case it was a flake

@14rcole
Copy link
Collaborator Author

14rcole commented Nov 1, 2024

/retest

@14rcole 14rcole force-pushed the update-application-api branch 13 times, most recently from b7b043e to fed7cf8 Compare November 4, 2024 20:51
The component status CRD had a new field to it, but application-service
would overwrite the field when anyone attempted to update it.  Updating
application-service to the newest version of application-api fixes
this issue

Signed-off-by: Ryan Cole <[email protected]>
@14rcole 14rcole force-pushed the update-application-api branch from fed7cf8 to d232108 Compare November 5, 2024 01:51
Copy link

sonarqubecloud bot commented Nov 5, 2024

@14rcole
Copy link
Collaborator Author

14rcole commented Nov 5, 2024

/test application-service-e2e

@dirgim dirgim self-requested a review November 5, 2024 13:51
Copy link

openshift-ci bot commented Nov 5, 2024

@14rcole: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/application-service-e2e d232108 link true /test application-service-e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link

@jencull jencull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link

openshift-ci bot commented Nov 5, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 14rcole, jencull
Once this PR has been reviewed and has the lgtm label, please ask for approval from johnmcollier. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@johnmcollier johnmcollier merged commit b5a8199 into redhat-appstudio:main Nov 5, 2024
10 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants