Support multiple vpc_id's when creating zone with route53_zone

[oucil]

ISSUE TYPE

• Feature Idea

COMPONENT NAME

route53_zone

ANSIBLE VERSION

ansible 2.3.0 (devel 14a2757116) last updated 2016/12/05 20:08:34 (GMT -400)
  lib/ansible/modules/core: (detached HEAD 6890003c4f) last updated 2016/12/05 20:08:36 (GMT -400)
  lib/ansible/modules/extras: (detached HEAD 20ea46642b) last updated 2016/12/05 20:08:37 (GMT -400)
  config file = ***
  configured module search path = Default w/o overrides

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

We keep our ansible machine in a totally separate VPC ("mgmt") from the Production VPC ("prod") that it manages so that we can bring up or pull down development deployments ("dev") without touching the production deployment.

Our playbook creates a new private zone in route53 for the new "dev" deployment, and includes the vpc_id, however, in order for ansible to have access to work with any of the instances we bring up in the new "dev" VPC, we need to ALSO attach the "mgmt" VPC to the Route53 zone so it can use the new hostnames. We need to be able to specify more than one vpc_id for the zone to be attached to.

STEPS TO REPRODUCE

- name: Create Route53 Private Zone
    route53_zone:
      region: "{{ aws.region }}"
      aws_access_key: "{{ aws.access_key }}"
      aws_secret_key: "{{ aws.secret_key }}"
      state: present
      zone: "{{ aws.route53_zone_internal }}"
      comment: "Dev internal DNS"
      # support list for input of vpc_id...
      vpc_id: ["{{ dev_vpc.vpc.id  }}","{{ aws.admin_vpc_id }}"]
      vpc_region: "{{ dev_vpc.vpc.region  }}"

EXPECTED RESULTS

Creation of a new Route 53 Zone, with 2 VPC ID's attached.

[ansibot]

This repository has been locked. All new issues and pull requests should be filed in https://github.com/ansible/ansible

Please read through the repomerge page in the dev guide.

[oucil]

This issue was moved to ansible/ansible#19114