Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1466 Inventory configuration precedence is confusing Change By: Lucy Wyman Labels: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315922.1562780625000.44522.1565109480638%40Atlassian.JIRA.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Kevin Reeuwijk commented on BOLT-1466 Re: Inventory configuration precedence is confusing Can you force override the transport by specifying '--transport pcp' as a workaround? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315922.1562780625000.12761.1562871420152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Lucy Wyman commented on BOLT-1466 Re: Inventory configuration precedence is confusing Making targets in the inventory context aware of how they are being invoked isn't feasible. When invoking a single group it's easy to know what context should take precedence - that of the group being invoked. But what if I invoke multiple groups that a node is a part of? Which group config should take precedence? What if I invoke the node by name, and it's a member of multiple groups? The inventory is fundamentally a way of storing connection information about targets. Groups are just ways of short-handing a list of those targets and providing some precedence to config options, but they don't (and, as far in the future as I can see, won't) provide the context for those targets to be run in during a particular Bolt invocation. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315922.1562780625000.12550.1562867220272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Dimitri Tischenko commented on BOLT-1466 Re: Inventory configuration precedence is confusing Just tested a work-around by placing the pcp group at the top of the inventory file. This effectively forces bolt to use the pcp transport for the nodes from puppetdb, but it creates an inverse problem: now, the transport for nodes defined further down in the inventoryfile is ignored - all nodes which are also member of the pcp group now connect over pcp. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315922.1562780625000.12070.1562836440086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title
Dimitri Tischenko commented on BOLT-1466
Re: Inventory configuration precedence is confusing
The confusion arises especially with dynamically populated groups. For instance, if using this group:
targets:
- _plugin: puppetdb
query: "nodes[] { }"
config:
transport: pcp
one would assume that all targets dynamically acquired by the puppetdb plugin will be guaranteed to connect over pcp. However, due to the way inventory parsing is implemented, if that node name is defined elsewhere in the inventory file with a different transport, bolt will prefer that definition which is not what the user expects.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Kevin Reeuwijk commented on BOLT-1466 Re: Inventory configuration precedence is confusing Shouldn't the (expected) behavior be that if -n groupname is specified, that Bolt scopes its use of the inventoryfile to that group only? Maybe the --nodes parameter is too ambiguous for this to work reliably, and a --group parameter is needed to more clearly communicate intent? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315922.1562780625000.12035.1562834880198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1466) Inventory configuration precedence is confusing
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1466 Inventory configuration precedence is confusing Issue Type: Task Assignee: Unassigned Created: 2019/07/10 10:43 AM Priority: Normal Reporter: Lucy Wyman If a node belongs to multiple groups in the inventory it will pick up config from the first group with that node in the inventory, event if `-n group2` is specified. This is expected but counterintuitive behavior. Questions: Should we document this exact case and explain in more detail inventory config? Is there a way to use `bolt inventory show` to help users find where config is coming from? Add Comment
