Skip to content

Conversation

@tthvo
Copy link
Member

@tthvo tthvo commented Jan 27, 2026

The PR is an incremental step to migrate AWS API calls to AWS SDK v2. This only focuses on CCO helpers in the pkg/asset and dependent pkg(s).

We import cloud-credential-operator (CCO) code to reuse its helpers to perform permission as a preflight validation.

Note: I only pinned the CCO version to one that has all the AWS SDK v2 changes. Latest CCO version has breaking changes to Azure client, which I hope to avoid.

tthvo added 3 commits January 27, 2026 13:51
go get github.com/openshift/cloud-credential-operator@a3e50aeacc55
The PR is an incremental step to migrate AWS API calls to AWS SDK v2.
This only focuses on CCO helpers in the pkg/asset and dependent pkg(s).

We import CCO code to reuse its helpers to perform permission as a
preflight validation.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 27, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 27, 2026

@tthvo: This pull request references CORS-4055 which is a valid jira issue.

Details

In response to this:

The PR is an incremental step to migrate AWS API calls to AWS SDK v2. This only focuses on CCO helpers in the pkg/asset and dependent pkg(s).

We import cloud-credential-operator (CCO) code to reuse its helpers to perform permission as a preflight validation.

Note: I only pinned the CCO version to one that has all the AWS SDK v2 changes. Latest CCO version has breaking changes to Azure client, which I hope to avoid.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from mtulio and rna-afk January 27, 2026 22:09
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign vr4manta for approval. For more information see the Code Review Process.

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

Details 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

@tthvo
Copy link
Member Author

tthvo commented Jan 27, 2026

/label platform/aws
/cc @patrickdillon @barbacbd @yunjiang29

@tthvo
Copy link
Member Author

tthvo commented Jan 28, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 28, 2026

@tthvo: The following tests 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/e2e-gcp-custom-endpoints 88969d3 link false /test e2e-gcp-custom-endpoints
ci/prow/e2e-gcp-xpn-dedicated-dns-project 88969d3 link false /test e2e-gcp-xpn-dedicated-dns-project
ci/prow/e2e-gcp-custom-dns 88969d3 link false /test e2e-gcp-custom-dns
ci/prow/e2e-aws-ovn-shared-vpc-edge-zones 88969d3 link false /test e2e-aws-ovn-shared-vpc-edge-zones
ci/prow/e2e-azurestack 88969d3 link false /test e2e-azurestack
ci/prow/e2e-gcp-ovn 88969d3 link true /test e2e-gcp-ovn
ci/prow/e2e-aws-ovn-heterogeneous 88969d3 link false /test e2e-aws-ovn-heterogeneous

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. platform/aws

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants