Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Future consideration
Categories Wazi Deploy
Created by Guest
Created on Aug 6, 2025

Introduce Wazi Deploy Config and Work directories

Wazi Deploy currently requires users to define their own strategy to maintain deployment configurations and work directories.

I would like to see a simplified approach leveraging standard config and work directories: 

Maintain a configuration directory such as /etc/wazideploy/conf directory for

  • logging configuration
  • tool configuration - such as the default encoding for output files
  • the default deployment method, 
  • the default artifact configuration file,
  • custom templates in a /templates directory 

This should leverage a WAZI_DEPLOY_CONF environment variable.

Maintain a default work directory ex.: /var/wazideploy/work  that is set up during the default installation/config process where the logger by default write into, and what is used as a temporary working directory (instead of having to pass this as a CLI option).

This should leverage a WAZI_DEPLOY_WORK environment variable.

This would allow to reduce the number of CLI parms required for the various Wazi Deploy commands.

Idea priority High