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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Allow environment variables in the plugin-cfg.xml file
Our customer is evaluating WebSphere Liberty 184.108.40.206 using the latest version v220.127.116.11 IHS + PLUGIN tar instalation package to develop an architecture for running WebSphere Liberty in a containerized environment. When we run the "pluginUtility generate ..." command we faced the problem that the hostname(s) etc. in the generated plugin-cfg.xml file are set to the host-name of the build host and can not be made variable. This is however not useable in a containerized environment when multiple containers are started as each of the containers has a different host names. Therefore extra code and plugin-cfg.xml manipulation is required before starting the containers.
Therefore it would be very helpful for us if the plugin code would be capable of processing (environment?) variables in the plugin-cfg.xml so that attributes in the plugin-cfg.xml can be easily adjusted to the currently running container.
Do not place IBM confidential, company confidential, or personal information into any field.