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

All the reference to the IBMCLOUD_API_KEY to be updated #666

Closed
mkumatag opened this issue Sep 19, 2024 · 9 comments
Closed

All the reference to the IBMCLOUD_API_KEY to be updated #666

mkumatag opened this issue Sep 19, 2024 · 9 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.

Comments

@mkumatag
Copy link
Member

What happened:

IBMCLOUD_API_KEY is been used in many places in the code, this needs to be fixed - https://github.com/search?q=repo%3Appc64le-cloud%2Fpvsadm%20IBMCLOUD_API_KEY&type=code

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • pvsadm version (use pvsadm version):
  • Environment - On-Prem or IBM PowerVS:
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Others:
@mkumatag mkumatag added the kind/bug Categorizes issue or PR as related to a bug. label Sep 19, 2024
@mkumatag
Copy link
Member Author

cc @kishen-v

@kishen-v
Copy link
Contributor

/good-first-issue

@ppc64le-cloud-bot
Copy link
Contributor

@kishen-v:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

@ppc64le-cloud-bot ppc64le-cloud-bot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Sep 19, 2024
@manju956
Copy link

/assign

@kishen-v
Copy link
Contributor

Hi @manju956,
Thanks for looking into this issue. We're deprecating the IBMCLOUD_API_KEY and will be usingIBMCLOUD_APIKEY instead.

All references need to refer IBMCLOUD_APIKEY.

Thanks!

@Karthik-K-N
Copy link
Contributor

Hi @manju956, Thanks for looking into this issue. We're deprecating the IBMCLOUD_API_KEY and will be usingIBMCLOUD_APIKEY instead.

All references need to refer IBMCLOUD_APIKEY.

Thanks!

Whats the reason for this change, Wanted to know because we follow similar format in CAPIBM.

@kishen-v
Copy link
Contributor

Hey @Karthik-K-N,
The go-sdk-core expects the API KEY to be exported as IBMCLOUD_APIKEY, at the package level, in order to use the same, we had to re-export the key from IBMCLOUD_API_KEY to IBMCLOUD_APIKEY to use the package. Hence, we are making the change.

pvsadm/cmd/root.go

Lines 49 to 52 in 5001afd

// TODO : deprecate IBMCLOUD_API_KEY for IBMCLOUD_APIKEY
// The GetAuthenticatorFromEnvironment requires "IBMCLOUD_APIKEY" to be set, apart from IBMCLOUD_API_KEY used in the project.
// In order to use the resourcecontrollerv2's functionality, the IBMCLOUD_API_KEY is re-exported as IBMCLOUD_APIKEY.
// Ref: github.com/ibm/go-sdk-core/[email protected]/core/config_utils.go, which is available from either from a credentials file, environment or VCAP service.

@kishen-v
Copy link
Contributor

Fixed via: #671

/close

@ppc64le-cloud-bot
Copy link
Contributor

@kishen-v: Closing this issue.

In response to this:

Fixed via: #671

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

5 participants