-
Notifications
You must be signed in to change notification settings - Fork 38
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
Comments
cc @kishen-v |
/good-first-issue |
@kishen-v: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
/assign |
Hi @manju956, All references need to refer Thanks! |
Whats the reason for this change, Wanted to know because we follow similar format in CAPIBM. |
Hey @Karthik-K-N, Lines 49 to 52 in 5001afd
|
Fixed via: #671 /close |
@kishen-v: Closing this issue. In response to this:
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. |
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
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: