Skip to content

Conversation

@sam-nguyen7
Copy link
Contributor

https://issues.redhat.com/browse/OSD-20603

Update osdctl account mgmt commands to use RH SSO credentials generated via https://github.com/app-sre/rh-aws-saml-login which spawns a new shell with the AWS_ACCOUNT_NAME environment variable.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 8, 2024
@sam-nguyen7
Copy link
Contributor Author

/hold for testing
assign command fails due to: error: operation error Organizations: CreateAccount, https response error StatusCode: 400, RequestID: bb0e1fda-4bed-411d-a2c4-1ad6d68594f5, AccessDeniedException: You don't have permissions to access this resource.

MR was created to add permission: https://gitlab.cee.redhat.com/service/app-interface/-/merge_requests/114730

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 8, 2024
Copy link
Contributor

@iamkirkbater iamkirkbater left a comment

Choose a reason for hiding this comment

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

Can I ask why we're going with osd-staging-1 and osd-staging-2-prod? Can we standardize on just being osd-staging-#? I specifically worry about osd-staging-2-prod because staging-2 is not prod and should not be used for any prod things.

Additionally can we pull osd-staging-1 and osd-staging-2 out into constants somewhere within osdctl that makes sense and reference them from that?

@sam-nguyen7
Copy link
Contributor Author

/label tide/merge-method-squash

@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Aug 21, 2024
@sam-nguyen7
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 22, 2024
Copy link
Contributor

@iamkirkbater iamkirkbater left a comment

Choose a reason for hiding this comment

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

Two small changes, one just a small nit about the usage of constants and the other just a better name for a var.

Thanks!

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 22, 2024

@sam-nguyen7: all tests passed!

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.

@iamkirkbater
Copy link
Contributor

/lgtm

Thanks for making the changes!

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 26, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 26, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamkirkbater, sam-nguyen7

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

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [iamkirkbater,sam-nguyen7]

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

@openshift-merge-bot openshift-merge-bot bot merged commit 2f187f3 into openshift:master Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants