Jira (BOLT-1328) AWS inventory discovery integration

32 views
Skip to first unread message

Lucy Wyman (JIRA)

unread,
May 21, 2019, 12:42:02 PM5/21/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
 
Puppet Task Runner / Task BOLT-1328
AWS inventory discovery integration
Change By: Lucy Wyman
Sprint: Bolt Kanban Ready for Grooming
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Lucy Wyman (JIRA)

unread,
May 21, 2019, 12:42:02 PM5/21/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Change By: Lucy Wyman
Summary: AWS dynamic inventory plugin discovery integration

Lucy Wyman (JIRA)

unread,
May 24, 2019, 1:46:04 PM5/24/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd :
* Tags

{code}
 target-lookups:
  - plugin: aws::ec2
    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
 {code}

Lucy Wyman (JIRA)

unread,
May 24, 2019, 1:57:03 PM5/24/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd:
* Tags

{code}
target-lookups:
  - plugin: aws::ec2
    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
    name: tag.name
    config:
       ssh:
          host: instance.ipAddress
          tmpdir: instance.tmpdir
 {code}
#### Questions:
Should we filter out terminated instances? Decide later, but maybe have an option to turn it off?

Lucy Wyman (JIRA)

unread,
May 24, 2019, 1:58:02 PM5/24/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd:
* Tags

{code}
target-lookups:
  - plugin: aws::ec2
    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
    name: tag.name
    config:
       ssh:
          host: instance.ipAddress
{code}

* * Questions* * :

Should we filter out terminated instances? Decide later, but maybe have an option to turn it off?

Lucy Wyman (JIRA)

unread,
May 24, 2019, 1:58:02 PM5/24/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd:
* Tags

{code}
target-lookups:
  - plugin: aws::ec2
    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
    name: tag.name
    config:
       ssh:
          host: instance.ipAddress
          tmpdir: instance.tmpdir
 {code}

 #### ** Questions ** :

Should we filter out terminated instances? Decide later, but maybe have an option to turn it off?

Lucy Wyman (JIRA)

unread,
May 24, 2019, 1:59:02 PM5/24/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd:
* Tags
Users should be able to reference instance data with { {instance.<attribute>}} in the {{name}}, {{uri}}, or {{config}}. They should also be able to set these to tag values using {{tags.<tag>}}.

{ code}

target-lookups:
  - plugin: aws::ec2
    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
    name: tag tags .name

    config:
       ssh:
          host: instance.ipAddress
{code}

*Questions*:

Should we filter out terminated instances? Decide later, but maybe have an option to turn it off?

Lucy Wyman (JIRA)

unread,
Jun 18, 2019, 12:40:02 PM6/18/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Change By: Lucy Wyman
Sprint: Bolt Ready for Grooming Kanban

Lucy Wyman (JIRA)

unread,
Jul 1, 2019, 6:18:03 PM7/1/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd:
* Tags

Users should be able to reference instance data with {{instance.<attribute>}} in the {{name}}, {{uri}}, or {{config}}. They should also be able to set these to tag values using {{tags.<tag>}}.

{code}
target-lookups targets :
  - plugin _plugin : aws::ec2

    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
    name: tags.name

    config:
       ssh:
          host: instance.ipAddress
{code}

*Questions*:
Should we filter out terminated instances? Decide later, but maybe have an option to turn it off?

Lucy Wyman (JIRA)

unread,
Jul 1, 2019, 6:21:02 PM7/1/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd:
* Tags

Users should be able to reference instance data with {{instance.<attribute>}} in the {{name}}, {{uri}}, or {{config}}. They should also be able to set these to tag values using {{tags.<tag>}}.

{code}
targets:
  - _plugin: aws::ec2

    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
    name: tags instance .name

    config:
       ssh:
          host: instance.ipAddress
{code}

*Questions*:
Should we filter out terminated instances? Decide later, but maybe have an option to turn it off?

Tom Beech (JIRA)

unread,
Jul 1, 2019, 6:26:02 PM7/1/19
to puppe...@googlegroups.com
Tom Beech assigned an issue to Tom Beech
Change By: Tom Beech
Assignee: Tom Beech

Lucy Wyman (JIRA)

unread,
Jul 1, 2019, 6:28:02 PM7/1/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Change By: Lucy Wyman
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd:
* Tags

Users should be able to reference instance data with {{instance.<attribute>}} in the {{name}}, {{uri}}, or {{config}}. They should also be able to set these to tag values using {{tags.<tag>}}.

{code}
targets:
  - _plugin: aws::ec2
    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
    name: instance.name

    config:
       ssh:
          host: instance.ipAddress
{code}

*Questions*:
Should we filter out terminated instances? Decide later, but maybe have an option to turn it off?


Config:
{code}
aws:
  token: foo
{code}

Tom Beech (JIRA)

unread,
Jul 3, 2019, 1:34:03 PM7/3/19
to puppe...@googlegroups.com
Tom Beech commented on Task BOLT-1328
 
Re: AWS inventory discovery integration

By default the aws-sdk-ec2 gem will return all instances, even if they're not running. Since non-running instaces do not have a public ip address or dns name, we probably want to filter these out. Another approach is to use the private ip address and dns name for any non-running instances, but I'm not sure how useful this is.

Lucy Wyman (JIRA)

unread,
Jul 8, 2019, 6:04:04 PM7/8/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.

We should have an inventory discovery integration that gets targets from AWS.
It should only get targets that are EC2 instances.
Users should have the ability to filter instances based on the following. Filters are and'd together, not or'd:
* Tags

Users should be able to reference instance data with {{instance.<attribute>}} in the {{name}}, {{uri}}, or {{config}}. They should also be able to set these to tag values using {{tags.<tag>}}.

{code}
targets:
  - _plugin: aws::ec2
    region: us-west2
    filter:
      - name: tag:Owner
        value: 'Cody'
      - name: tag-key # Anything that has OtherKey tag defined
        value: OtherKey
    name: instance.name
    config:
       ssh:
          host: instance.ipAddress
{code}

*Questions*:
Should we filter out terminated instances? Decide later, but maybe have an option to turn it off?

Config:
{code}
aws:
  token: foo
{code}

Tom Beech (JIRA)

unread,
Jul 11, 2019, 7:42:03 PM7/11/19
to puppe...@googlegroups.com
Tom Beech updated an issue
Change By: Tom Beech
Fix Version/s: BOLT Next

Chris Cowell (JIRA)

unread,
Jul 25, 2019, 4:19:03 PM7/25/19
to puppe...@googlegroups.com
Chris Cowell updated an issue
Change By: Chris Cowell
Labels: docs_reviewed
Reply all
Reply to author
Forward
0 new messages