ansible-collections / ansible-collections/google.cloud
Add support for VPC Peering Connections
- Dominant language
- Python
- Stars
- 105
- Forks
- 144
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 4
Description
##### SUMMARY
Given the prevalence of CloudSQL usage, it would be helpful if a full setup could be achieved for this using Ansible.
Presently the instructions to complete Private Service Access do not appear to be completable using the Ansible Collection, specifically CLI command 'gcloud services vpc-peerings' is not covered.
https://cloud.google.com/vpc/docs/configure-private-services-access
##### ISSUE TYPE
- Feature Idea
##### COMPONENT NAME
google.cloud.services_vpc_peering
##### ADDITIONAL INFORMATION
A typical cmd to do this in bash might look like:
gcloud compute addresses create google-managed-services-${network_name} --global --purpose=VPC_PEERING --addresses=10.0.0.0 --prefix-length=19 --network=${network_name}
gcloud services vpc-peerings connect --service=servicenetworking.googleapis.com --ranges=google-managed-services-${network_name} --network=${network_name} --project=${project}
```yaml
```
Contributor guide
Research direction
Start with the google.cloud.services_vpc_peering component and the linked Google Cloud Private Service Access instructions. Compare the two supplied gcloud commands with the collection's existing module entry points and determine how their inputs should be represented. Done means a playbook can create the reserved address range and establish the service networking VPC peering without manual CLI steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, google-cloud, python
- Domain
- cloud, devops, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100