Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Future consideration
Created by Guest
Created on Aug 28, 2023

For the zAPM Openshift-hosted components, add support for externally-vaulted secrets data such as via Hashicorp Vault for environments where local secrets use is not permitted.

This would be useful for compliance/controls requirements where local Openshift secrets are not permitted.   Managed secrets such as externally-vaulted secrets data with access controls are one example of a compliant solution.

Benefit is to allow accepted use of zAPM where local secrets run afoul of compliance mandates and avoid risk acceptance or prevent overall product rejection from the secrets setup.

Examples of how this could work: 
- native support for vaulted secrets data with hooks directly in zAPM, or
- support addition of init container or sidecar or injector into IBM pods handling retrieval of the secret key/value pairs, with support for removing the underlying local secrets once env or volumes are present with the equivalent secret data pulled from a vault

 

Idea priority Low