puppetlabs/vmpooler-provider-gce
2
0
Fork 0
mirror of https://github.com/puppetlabs/vmpooler-provider-gce.git synced 2026-01-26 11:28:41 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Adding the cloud DNS API library and related methods

Browse source 
we setup DNS when a VM is created and tear it down when a VM is deleted
the DNS zone should exist already and is referenced by a provider setting
the dns zone is also set in order to use it for vm_ready? instead of the global
domain
instances have a label that identifies which project they belong to, so
it can be used for FW rules
This commit is contained in:
Samuel Beaulieu 2021-12-29 08:13:32 -06:00
parent f6ec318b2d
commit daa55fe5b8
No known key found for this signature in database
GPG key ID: 12030F74136D0F34
9 changed files with 167 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

38
scripts/GCE_custom_role_for_SA.yaml Normal file
View file

@ -0,0 +1,38 @@
title: Custom vmpooler provider
description: for the vmpooler provider
stage: GA
includedPermissions:
- compute.disks.create
- compute.disks.createSnapshot
- compute.disks.delete
- compute.disks.get
- compute.disks.list
- compute.disks.setLabels
- compute.disks.use
- compute.instances.attachDisk
- compute.instances.create
- compute.instances.delete
- compute.instances.detachDisk
- compute.instances.get
- compute.instances.list
- compute.instances.setLabels
- compute.instances.start
- compute.instances.stop
- compute.snapshots.create
- compute.snapshots.delete
- compute.snapshots.get
- compute.snapshots.list
- compute.snapshots.setLabels
- compute.snapshots.useReadOnly
- compute.subnetworks.use
- compute.zoneOperations.get
- dns.changes.create
- dns.changes.get
- dns.changes.list
- dns.managedZones.get
- dns.managedZones.list
- dns.resourceRecordSets.create
- dns.resourceRecordSets.update
- dns.resourceRecordSets.delete
- dns.resourceRecordSets.get
- dns.resourceRecordSets.list