Upstream bug component is Provisioning
I think there are no plans for extending global parameters. In future they should be merged to smart variables which supports this already (but currently, smart variables are tied with puppet classes). You could probably use smart variable for this purpose already today, it's just a bit confusing that you need to assign puppet class and use hostgroup matcher. To monitor the unification, you can look watch this upstream ticket http://projects.theforeman.org/issues/12950
Upstream bug assigned to firstname.lastname@example.org
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
I'm using the global parameters to provide a list of hosts consuming the same content. This lets me provide a simple variable for setting up basic clustering.
Example: Add a new host to the MariaDB Galera content view and puppet automatically adds it into the firewall, config, etc.
<% begin -%><% if @host.content_view.system_names -%>[<% @host.content_view.system_names.sort.each do | hostname | -%>'<%= hostname %>',<% end -%>]<% end -%><% rescue => e -%><% end -%>
How would I do this with the unification noted in https://projects.theforeman.org/issues/12950 ?
I am re-opening this BZ ticket as the pull-request is already opened by me.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Rich Jerrido or Bryan Kearney or your account team. If we do not hear from you, we will close this bug out. Thank you.
Per comment 12, there is a PR upstream. Keeping open.
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/4127 has been resolved.
Here, I am considering list/dictionary nothing but array/hash type.
Yes, with this BZ fix, global parameters will support same types as smart class parameters.
Type list also includes array, hash, json and yaml.
Verified on Satellite 6.6 snap 6, support for various parameter types has been added to hostgroups
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.