Hi Team,
I was doing a POC where I deleted Push Notification instance and then I restored it by doing steps mentioned in below document.
https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resource#ibmcloud_resource_reclamations
Apparently service credentials did not recovers those were attached to this instance, for read and writer access.
It has to restore service credentials as well.
below is the impact if it didn't restore service credentials:
Impact: if the service credentials are not restored, we cannot send push notifications anymore from back-end and the mobile application cannot connect as well. This means a very long interruption, the time to redeploy the back-end, and even more to publish a new application.
can you bring this feature by considering with a high priority.
Thanks,
Ankur
| Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
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" ?