This portal is to open public enhancement requests against IBM Cloud and its products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
IBM Cloud Support Center (https://cloud.ibm.com/unifiedsupport/cases/form) – Use this site for any IBM Cloud defect or support need.
Stack Overflow (https://stackoverflow.com/questions/tagged/ibm-cloud) – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud".
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi Justin,
While creating new service credentials in restored instance then only the api key is changing rest is same as before.
I think we can manage only for API key to have new one on restored instance.
You may close this request, I shall open a new request if needed for same in future.
Thanks,
Ankur Garg
Hello Ankur,
This is working as expected. For any service that is deleted and then restored, we determined as part of the archiecture that was something we cannot accomodate
There were many factors at play here, including:
1. The serivce instance, binding and key are different objects and we don’t want to incidentally disrupt status during retention period. this was a large concern that we couldn't ensure
2. the binding and key can be recreated easily
3. removing them won’t cause any customer data loss and that was our primary goal
Can you let me know how difficult it was to re-establish service credentials manually? is this a case where you just needed to know this ahead of time and could account for it when restoring the service had you known from the document you referenced above?
What do you mean by this status "Will not implement - Provided workaround" ?