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.


Add a new idea Subscribe
Status Submitted
Workspace DevOps Automation
Categories Deploy
Created by Guest
Created on Nov 5, 2026

RELATED IDEAS

Dynamic artifact filtering by metadata/manifest for z/OS deployments across multi-target LPARs

Problem: We deploy to two production LPARs where compiled members target LPAR A, LPAR B, or both, as defined by a sidecar .yml file. Because IBM DevOps Deploy cannot conditionally filter members during deployment based on target resource properties, we must split artifacts into separate PDS datasets at build time. In lower/shared environments, this causes duplicate deployments of shared members, wasting time and MIPS.

Proposed Solution: Enable deployment steps to read member metadata (sidecar YAML) and filter what gets deployed based on target resource properties (e.g., LPAR name). A single component should dynamically deploy only the relevant members to each LPAR without requiring separate pre-split datasets.

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.