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 Under review
Workspace DevOps Automation
Categories Deploy
Created by Guest
Created on Oct 31, 2025

RELATED IDEAS

Ability to Set tomcat.keystore.password During Unattended Installation

My client uses Puppet to automate the installation of DevOps Deploy instances. Currently, after installation, they need to manually update the secured-installed.properties file to modify the tomcat.keystore.password entry. This post-installation step adds unnecessary complexity to the automated deployment process.

It would be ideal if the installer supported specifying this password in the server’s install.properties file, so it could be automatically written to secured-installed.properties during installation.

During testing, they observed that the installer currently sets the default password (changeit) automatically, which suggests the process is already capable of writing the value — it’s just not configurable at install time.

Could you please confirm whether there are any plans to support this property in unattended installations, or if it could be considered for a future enhancement?

For reference, here’s the command they are using to perform the installation: /dod_shared/installer/devops-deploy-install/install-server.sh -silent -install-dir /opt/IBM/devops_deploy/server

  • Admin
    Randy Langehennig
    Nov 21, 2025

    Thank you for submitting this idea to our team. We are creating a discussion topic and will review with the development team soon. We will be in touch with updates. The idea is now in 'Under review' state.

    Reply

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.