Description of problem:
Support setting projectRequestMessage through a playbook variable that can be referenced in an inventory file.
Customer feels the current method of requiring an administrator to manually modify master-config.yaml and restart api services to be cumbersome.
Related to bug 1659141.
This is already possible in 3.11 setting osm_project_request_message variable in the inventory file.
Re-opening as a documentation bug. Document use of setting osm_project_request_message variable in the inventory file.
(In reply to Jack Ottofaro from comment #7)
> Any updates?
As soon as 4.1 is out. :)
The PR's here: https://github.com/openshift/openshift-docs/pull/15265
Jianlin, will you PTAL? The values are based on the information from https://docs.openshift.com/container-platform/3.11/install_config/master_node_configuration.html#master-node-config-project-config
I'm waiting for a peer review before I merge.
This change is live on docs.openshift, eg https://docs.openshift.com/container-platform/3.11/install/configuring_inventory_file.html#configuring-project and https://docs.openshift.com/container-platform/3.6/install_config/install/advanced_install.html