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 Functionality already exists
Workspace DataPower Gateway
Created by Guest
Created on Mar 19, 2025

How to handle common files and credential file ( xml, js and xslt format ) in GitOps ?

1. We have more than 100 files like error handlings or message in xslt. Can we upload these in store:// folder which can be visible to every domain ?

2. We have also some credential files in local folder for few domains. How can we handle these credential file ? If we upload them in store folder it will be accessible to every domain. We don't want it to be accessible in other domain. It is domain specific.

Idea priority High
  • Admin
    Ulas Cubuk
    Mar 5, 2026
    You handle common files and credential artifacts in DataPower GitOps by treating them as part of the domain’s “local files” and/or as GitOps templates, plus using externalized secrets rather than committing real credentials.
    What GitOps in DataPower actually versions
    * A GitOps write persists the full domain configuration plus the domain’s local:// filesystem (stylesheets, GatewayScript, XML, JS, XSLT, etc.) into the Git repository as JSON and file content.
    * The Git repo normally has a datapower/ (or similar) root, under which there is a GitOps directory tree; local files for the domain are included automatically on gitops-write.
    This means XML config fragments, JS, and XSLT that you currently keep under local:// can all be driven by GitOps without special handling.[See: Apply GitOps principles to DataPower]