IBM Cloud - Structured Ideas

Shape the future of IBM!

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you

  1. Post an idea

  2. Vote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

NOTE: All IBM employees must enter Ideas through this Ideas Portal.

Push Notification - restore service credentials

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

  • Guest
  • Jun 29 2020
  • Not under consideration
Idea priority High
  • Guest commented
    30 Jul, 2020 12:59am

    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

  • Admin
    JUSTIN KRUGER commented
    29 Jul, 2020 06:53pm

    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?

  • Guest commented
    29 Jul, 2020 12:50am

    What do you mean by this status "Will not implement - Provided workaround" ?

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.