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

Jump to bottom

Feature: Terraform script to set and reset the ks api-key #2118

Closed
indirakalagara opened this issue Dec 16, 2020 · 2 comments
Closed

Feature: Terraform script to set and reset the ks api-key #2118

indirakalagara opened this issue Dec 16, 2020 · 2 comments
Assignees
@kavya498

Comments

@indirakalagara
Copy link

Hi Team,

Customer is looking for the terraform equivalent of the following ibmcloud cli command  to set "ks api-key"
ibmcloud ks api-key reset --region

https://cloud.ibm.com/docs/containers?topic=containers-users#api_key_most_cases

Request you to add this feature on priority to address the customer needs.
@indirakalagara indirakalagara changed the title Terraform script to set and reset the ks api-key Feature: Terraform script to set and reset the ks api-key Dec 16, 2020
@kavya498 kavya498 self-assigned this Dec 30, 2020
kavya498 added a commit to kavya498/terraform-provider-ibm that referenced this issue Dec 30, 2020
@kavya498
Support IBM-Cloud#2118: KS APIkey Reset
ec09ed0
kavya498 added a commit to kavya498/terraform-provider-ibm that referenced this issue Dec 30, 2020
@kavya498
Support IBM-Cloud#2118: Latest Vendor
83a0da8
hkantare pushed a commit that referenced this issue Dec 30, 2020
@kavya498 @hkantare
Support #2118: KS APIkey Reset
381154f
hkantare pushed a commit that referenced this issue Dec 30, 2020
@kavya498 @hkantare
Support #2118: Latest Vendor
4cd68a3
@kavya498
Copy link
Collaborator

Available in Latest 1.19.0

@hkantare
Copy link
Collaborator

closing the issue

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

@kavya498 kavya498

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@indirakalagara @hkantare @kavya498