{"action":"created","issue":{"url":"https://api.github.com/repos/ansible/ansible-modules-core/issues/1385","labels_url":"https://api.github.com/repos/ansible/ansible-modules-core/issues/1385/labels{/name}","comments_url":"https://api.github.com/repos/ansible/ansible-modules-core/issues/1385/comments","events_url":"https://api.github.com/repos/ansible/ansible-modules-core/issues/1385/events","html_url":"https://github.com/ansible/ansible-modules-core/pull/1385","id":78676326,"number":1385,"title":"Adding ability to filter AWS Route 53 private hosted zones by attache…","user":{"login":"joelthompson","id":1562980,"avatar_url":"https://avatars.githubusercontent.com/u/1562980?v=3","gravatar_id":"","url":"https://api.github.com/users/joelthompson","html_url":"https://github.com/joelthompson","followers_url":"https://api.github.com/users/joelthompson/followers","following_url":"https://api.github.com/users/joelthompson/following{/other_user}","gists_url":"https://api.github.com/users/joelthompson/gists{/gist_id}","starred_url":"https://api.github.com/users/joelthompson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joelthompson/subscriptions","organizations_url":"https://api.github.com/users/joelthompson/orgs","repos_url":"https://api.github.com/users/joelthompson/repos","events_url":"https://api.github.com/users/joelthompson/events{/privacy}","received_events_url":"https://api.github.com/users/joelthompson/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/ansible/ansible-modules-core/labels/cloud","name":"cloud","color":"c7def8"},{"url":"https://api.github.com/repos/ansible/ansible-modules-core/labels/feature_pull_request","name":"feature_pull_request","color":"009800"},{"url":"https://api.github.com/repos/ansible/ansible-modules-core/labels/needs_info","name":"needs_info","color":"eb6420"},{"url":"https://api.github.com/repos/ansible/ansible-modules-core/labels/P3","name":"P3","color":"fef2c0"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-05-20T20:07:02Z","updated_at":"2015-07-10T05:06:07Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/ansible/ansible-modules-core/pulls/1385","html_url":"https://github.com/ansible/ansible-modules-core/pull/1385","diff_url":"https://github.com/ansible/ansible-modules-core/pull/1385.diff","patch_url":"https://github.com/ansible/ansible-modules-core/pull/1385.patch"},"body":"…d VPC\r\n\r\n##### Issue Type:\r\n\r\nFeature Pull Request\r\n\r\n##### Ansible Version:\r\n\r\ndevel\r\n\r\n##### Ansible Configuration:\r\n\r\nN/A\r\n\r\n##### Environment:\r\n\r\nN/A\r\n\r\n##### Summary:\r\n\r\nAWS allows you to configure multiple Route53 private hosted zones with the same zone name. The limitation is that multiple private hosted zones with the same name cannot be attached to the same VPC. This feature allows you to take advantage of this, filtering which private hosted zone you wish to make modifications on by attached VPC.\r\n\r\n##### Steps To Reproduce:\r\n\r\n```yaml\r\n- route53:\r\n      command: create\r\n      zone: foo.com\r\n      record: new.foo.com\r\n      type: A\r\n      ttl: 7200\r\n      value: 1.1.1.1\r\n      private_hosted_zone: true\r\n      vpc_id: vpc-xxxxxx\r\n```\r\n\r\n##### Expected Results:\r\n\r\nCreates new.foo.com in the foo.com private hosted zone attached to vpc-xxxxxx\r\n\r\n##### Actual Results:\r\n\r\nN/A"},"comment":{"url":"https://api.github.com/repos/ansible/ansible-modules-core/issues/comments/120227354","html_url":"https://github.com/ansible/ansible-modules-core/pull/1385#issuecomment-120227354","issue_url":"https://api.github.com/repos/ansible/ansible-modules-core/issues/1385","id":120227354,"user":{"login":"bennojoy","id":315687,"avatar_url":"https://avatars.githubusercontent.com/u/315687?v=3","gravatar_id":"","url":"https://api.github.com/users/bennojoy","html_url":"https://github.com/bennojoy","followers_url":"https://api.github.com/users/bennojoy/followers","following_url":"https://api.github.com/users/bennojoy/following{/other_user}","gists_url":"https://api.github.com/users/bennojoy/gists{/gist_id}","starred_url":"https://api.github.com/users/bennojoy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bennojoy/subscriptions","organizations_url":"https://api.github.com/users/bennojoy/orgs","repos_url":"https://api.github.com/users/bennojoy/repos","events_url":"https://api.github.com/users/bennojoy/events{/privacy}","received_events_url":"https://api.github.com/users/bennojoy/received_events","type":"User","site_admin":false},"created_at":"2015-07-10T05:06:07Z","updated_at":"2015-07-10T05:06:07Z","body":"@joelthompson  did some testing and looks good, couple of things, if a user sets vpc_id it automatically means that he wants to operate on a hosted zone in private , so can't we just make the private_zone to True so that the user doesnt have to enter that value explicitly to true. seems a but redundant to me.\r\nincase i missed something and private_zone is required to be set explicitlyfor some reason  then may be change this error message \"parameter 'private_zone_in' must be true when specifying parameter\" \" 'vpc_id_in'\" to the real module parameter names 'private_zone' and 'vpc_id' as the suffix _in is the variable name that user doesnt know about.\r\n\r\n"}}