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 Dec 2, 2024

Deployment of projects using CICD pipelines implemented using Admin reference APIs, post import of project to target tenant, connector and useraccount needs to be configured without editing to update flowservices.

Since CICD implementation to automate deployments are some of the regulatory and compliance needs of Banking, Insurance and Financial domain customer, but with the need to configure user accounts on connectors, post this update flowservices using connectors and user accounts can be risky and this does not serve the purpose why COCD implementations are beneficial as post deployment activities like creating connector, user accounts and unfortunately even editing code in prod env cant be avoided which is risky.

This is useful as this avoids the risk of changes to code post deployment to production env. Benefit for Customers as they are enabled with product features to be compliant with regulatory mandates.

We should avoid manual configuration and explicit editing of connectors, user accounts and editing code in prod as post deployment activity, instead Admin reference APIs should handle this.

Idea priority Urgent