- Host Collections that are dynamic (so if a parameter changes, a fact changes or a hosts hostgroup etc changes the hosts are added / removed) - Parameters which can be defined as types - hash, array, boolean etc. - Expose the version of a content view as a parameter - Matchers which can match against types (so check if a string is IN an array - when you have structured facts for example) - Allow structured facts to be searchable with regards to their type (subtly related to the above) - Allow default values for puppet parameters to be set where parameters can (for example, locations etc) (this would save on having a matcher which says if location = <location> <value> or obfuscating this into the puppet parameter with something like <%= YAML.load(@host.params['<name>']) %> - Add provisioning templates etc to the promotion / publish process. This way if we have a lifecycle of ENG -> TEST -> PROD we can test new partition tables, kickstart templates, snippets etc in the ENG environment without impacting other environments.
- A concerted effort to fix all the bugs as opposed to adding new features! And: On Wednesday, December 7, 2016 at 9:51:27 AM UTC-5, Jason B. Nance wrote: > > > - Add ability to merge parameters that come from org/location/OS/host > collection/host/etc,etc (like you can do with Class Parameters) > +1 > - Ability to go back to "normal" Foreman interface from the Dynflow > console, or better integration (so that you can deal with failed tasks > easier) > +1 -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
