https://github.com/flaconi/ansible-role-aws-vpc-peering

Creates and accepts vpc peerings
https://github.com/flaconi/ansible-role-aws-vpc-peering

ansible ansible-role aws role vpc vpc-peering

Last synced: 3 months ago
JSON representation

Creates and accepts vpc peerings

• Host: GitHub
• URL: https://github.com/flaconi/ansible-role-aws-vpc-peering
• Owner: Flaconi
• License: apache-2.0
• Created: 2018-05-22T09:54:13.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2023-02-13T16:55:24.000Z (almost 2 years ago)
• Last Synced: 2023-03-01T19:23:34.382Z (almost 2 years ago)
• Topics: ansible, ansible-role, aws, role, vpc, vpc-peering
• Language: Python
• Homepage:
• Size: 24.4 KB
• Stars: 2
• Watchers: 26
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Peering

Create and accept VPC Peering

[![Build Status](https://travis-ci.org/Flaconi/ansible-role-aws-vpc-peering.svg?branch=master)](https://travis-ci.org/Flaconi/ansible-role-aws-vpc-peering)

[![Version](https://img.shields.io/github/tag/Flaconi/ansible-role-aws-vpc-peering.svg)](https://github.com/Flaconi/ansible-role-aws-vpc-peering/tags)

[![Ansible Galaxy](https://img.shields.io/ansible/role/d/25995.svg)](https://galaxy.ansible.com/Flaconi/aws-vpc-peering/)

## Requirements

* Ansible 2.5

## Additional variables

Additional variables that can be used (either as `host_vars`/`group_vars` or via command line args):

| Variable                                | Description                  |

|-----------------------------------------|------------------------------|

| `aws_vpc_peering_profile`               | Boto profile name to be used |

| `aws_vpc_peering_default_region`        | Default region to use        |

| `aws_vpc_peering_vpc_filter_additional` | Additional `key` `val` filter to add to `vpc_acc_filter`, `vpc_acc_name`, `vpc_req_filter` and `vpc_req_name` by default. |

## Example definition

#### With sane defaults

When using the sane defaults, the only thing to configure for each peering is:

* the peering name

* the name or filter of the peering requester

* the name or filter of the peering accepter

```yml

aws_vpc_peering:

  - name: my-peering-1

    req_filter:

      - key: "tag:Name"

        val: vpc-1

      - key: "tag:Env"

        val: production

    acc_filter:

      - key: "tag:Name"

        val: vpc-2

      - key: "tag:Env"

        val: production

  - name: my-peering-2

    req_name: vpc-1

    acc_name: vpc-2

```

#### Customized array

Instead of using somebody's sane defaults, you can also fully customize your peering.

```yml

# Ensure VPC filter (name or filter) includes that the VPC is created already

# (not pending nor deleted)

aws_vpc_peering_vpc_filter_additional:

  - key: state

    val: available

aws_vpc_peering:

  - name: my-peering-1

    req_filter:

      - key: "tag:Name"

        val: vpc-1

      - key: "tag:Env"

        val: production

    acc_filter:

      - key: "tag:Name"

        val: vpc-2

      - key: "tag:Env"

        val: production

    region: eu-central-1

    tags:

      - key: env

        val: production

      - key: department

        val: devops

  - name: my-peering-2

    req_name: vpc-1

    acc_name: vpc-2

    region: eu-central-1

    tags:

      - key: env

        val: production

      - key: department

        val: devops

```

## Testing

#### Requirements

* Docker

* [yamllint](https://github.com/adrienverge/yamllint)

#### Run tests

```bash

# Lint the source files

make lint

# Run integration tests with default Ansible version

make test

# Run integration tests with custom Ansible version

make test ANSIBLE_VERSION=2.4

```