Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Submitted
Created by Guest
Created on Feb 5, 2026

Provide an IBM-owned URL for Updating OLM CatalogSource YAML Files

It would be beneficial to be able to supply an IBM-owned location for applying updates to the CatalogSource for the Operators (but also other configurations that must be applied based on IBM template YAML). Some customers block all "raw" paths. 

Here is the CP4I documentation related to updating catalog sources: https://www.ibm.com/docs/en/cloud-paks/cp-integration/16.1.3?topic=images-adding-catalog-sources-openshift-cluster

Take App Connect for example. The command to apply the new catalog source for the updated operator v12.19.0 is:

oc apply --filename https://raw.githubusercontent.com/IBM/cloud-pak/master/repo/case/ibm-appconnect/12.19.0/OLM/catalog-sources.yaml

The CatalogSource points back to the IBM Container Registry and customers would like the ability to have an alternative and preferably automated manner in picking up these new Catalog Sources where the "raw" path is blocked by their security teams. This results in manual effort to research, find, download, and apply all relevant elements and essentially creates an air-gapped environment because the config YAMLs are unavailable.

Idea priority Medium