Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Michael Smith Release Notes Summary: Bolt can now accept different transport configuration for targets through the inventory filr file Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Release Notes Summary: Bolt can now accept different transport configuration for targets through the inventory filr Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: David Kramer Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The default location for the inventory file is ~/.puppetlabs/bolt/inventory.yaml- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. - Bolt should not error with an invalid inventory file or one where the version is not '1.0' .(unexpected keys do not make an Inventory invalid)h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical specsee: https://docs.google.com/document/d/1V2LwAit-17GxWMrfPW7qFMwSdSnaJ7NdUEywNNVPlJM/edith2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. - Bolt should not error with an invalid inventory file or one where the version is not '1.0' .(unexpected keys do not make an Inventory invalid)h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical spec It will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges see: https://docs . At this stage we should prioritize a robust schema for API use over user friendliness to some extent google . We will handle easy to write formats in later tickets. com/document/d/1V2LwAit-17GxWMrfPW7qFMwSdSnaJ7NdUEywNNVPlJM/edit example file: h2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. - Bolt should not error with an invalid inventory file or one where the version is not '1 . 0' .(unexpected keys do not make an Inventory invalid) h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical specIt will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges. At this stage we should prioritize a robust schema for API use over user friendliness to some extent. We will handle easy to write formats in later tickets. example file:h2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. - Bolt should not error with an invalid inventory file. h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical specIt will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges. At this stage we should prioritize a robust schema for API use over user friendliness to some extent. We will handle easy to write formats in later tickets. example file:h2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories 1. I want to make lists of nodes in a file and target them by name. 2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical specIt will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges. At this stage we should prioritize a robust schema for API use over user friendliness to some extent. We will handle easy to write formats in later tickets. example file:h2. Out of scope:- Using groups names for targetting- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories1. I want to make lists of nodes in a file and target them by name.2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file.- {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical spec It will be a structured yaml file ideally using arrays over lists to enforce a clear priority order for merges. At this stage we should prioritize a robust schema for API use over user friendliness to some extent. We will handle easy to write formats in later tickets. example file: h2. Out of scope:- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.- user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories1. I want to make lists of nodes in a file and target them by name.2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements - The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config file. - {{--nodes}} options for bolt should accept group names as shorthand for the list of nodes they contain.- The run_* functions should accept group names in their target arrays- When connecting to a node configuration from the inventory should be used. h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. format and technical spec h2. Out of scope:- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan. - user friendly data format.- nested groups
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories1. I want to make lists of nodes in a file and target them by name.2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config- h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- url highesth3. formath2. Out of scope:- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
h2. Stories1. I want to make lists of nodes in a file and target them by name.2. I want to to configure node specific connection values.Bolt should support a structured data inventory file to allow users to refer to groups of nodes on the commandline and from plans. h2. Requirements- The location of the file should be specified with {{\-\-inventoryfile}} on the CLI or {{inventoryfile}} in the config- h3. Precedence order for connnection optionslowest- config file- cli flags- inventory- urlhighesth3. formath2. Out of scope:- Globs for specifying nodes- Consistent merging when config information is specified in multiple places- referring to the same hostname with different users or transports in the inventory.- setting other variables on nodes- updating any inventory information during a plan.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-104
Support inventory file in bolt
Change By:
Alex Dreyer
As soon as they get into nontrivial plans, users face a common pattern of needing to map different roles used inside the plan to concrete lists of hosts, which are usually provided dynamically by the executor. In Ansible this is a first-class plugin point called "inventory" and the introductory way to do it is with INI style flat files with a section header containing the role name, a list of hosts below that:{code}[webservers]web01.domain.comweb02.domain.com{code}which is then referenced inside the playbook as {code:yaml} hosts: webservers remote_user: root tasks: - name: ensure apache is at the latest versionyum: name=httpd state=latest - name: write the apache config filetemplate: src="" />{code}This lets users provide different sets of nodes without changing the playbook, akin to the data/code separation that Hiera provides for Puppet. It'll be super important to develop a way to perform this type of mapping, preferably with a combination of conventions ("the roles you use in a plan should be exposed in the plan as parameters of type {{Nodes}}") and an easy way to develop and use plugins to different inventory sources.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
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
Jira (BOLT-104) Support inventory file in bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Summary: Design conventions for mapping roles to nodes Support inventory file in plans bolt Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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. For more options, visit https://groups.google.com/d/optout.
