Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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).


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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Workspace DevOps Automation
Categories Deploy
Created by Guest
Created on Jun 5, 2026

Allow Snapshot Creation from Actual Current Inventory During Active Deployment Execution

Currently, when a snapshot is created during an Application Process using APIs such as:

/cli/snapshot/createSnapshotOfEnvironment

the generated snapshot reflects the deployment's target inventory ("Versions to Deploy") rather than the actual versions currently installed in the environment before deployment.

Based on discussions with IBM Support, this behavior is working as designed because the environment inventory is updated to the target deployment versions before process steps are executed.

However, this behavior is functionally incorrect for rollback and recovery use cases.

A snapshot created before or during deployment is expected to represent the actual currently installed versions in the environment at that point in time. In our scenario, the snapshot instead captures the configured “Versions to Deploy”, even before those versions are fully deployed and validated in the environment.

This creates a logical inconsistency from a deployment and rollback perspective:

  • the snapshot no longer represents the true pre-deployment state

  • rollback cannot reliably restore the original environment

  • before/after version tracking becomes inaccurate

  • automated recovery workflows become unsafe

Effectively, the snapshot reflects the intended target state rather than the actual existing state of the environment. If the inventory is updated to the target versions before deployment completion, then the snapshot generated at that stage cannot be considered a reliable snapshot.

We also understand from your confirmation that there is currently no API available to reset or reconstruct the snapshot inventory afterward.

Based on the current behavior and the absence of a supported API/workaround, this appears to be a product limitation for automation-driven rollback scenarios.

Possible implementation examples:

  • Additional API parameter:
    inventorySource=currentInstalled

  • Additional UI option:
    "Create snapshot from current installed inventory"

Expected Result:

Users should be able to create a snapshot during an active deployment process that accurately reflects the actual environment state before deployment changes are applied.

  • Admin
    Randy Langehennig
    Jul 24, 2026

    Our development team reviewed this request as it was written above. Our development team believes that perhaps there is a misunderstanding of how snapshots work. Snapshots capture the "desired inventory" and the snapshot taken at the end of a process is inherently sufficient to capture the desired state. The team concluded that a pre-deployment snapshot is redundant and that the customer should be advised that the post-process snapshot is enough for their needs. There is also concern that a manual, pre-deployment snapshot has a high risk of user error.

    As a result, we are moving this idea to the 'Not under consideration' state based on the text provided in this idea that we could read. It is possible we are not grasping something in your request and if so, please add a comment and we will review this once more. Feel free to send an email to rlange@ibm.com as well directly with this detail.

  • Admin
    Randy Langehennig
    Jun 30, 2026

    We are creating a discussion topic for this and will be reviewing this with our development team this week. Moving this to the 'Under review' state.

  • Admin
    Randy Langehennig
    Jun 25, 2026

    Thank you for submitting this idea. We will be creating a discussion topic to review this with our development team soon. This idea seems related to DVOPS-I-875 as well. We will be in touch I believe next week.