* first shot, untested
* example tests working
* module tests
* work on gke blueprints
* multitenant fleet doc examples
* fix gke hub doc examples
* blueprint tests
* move master range to vpc config
* fast stage 3 gke test
* tfdoc
* bump provider versions
* and bump provider again to latest
* Instance.ip_range cannot take Support CIDR
Current docs are incorrect. It is not possible to specify the Support range.
See https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.instances#Instance
> ipRange
> string
> Optional. IP range represents the customer-provided CIDR block of length 22 that will be used for the Apigee instance creation. This optional range, if provided, should be freely available as part of larger named range the customer has allocated to the Service Networking peering. If this is not provided, Apigee will automatically request for any available /22 CIDR block from Service Networking. The customer should use this CIDR block for configuring their firewall needs to allow traffic from Apigee. Input format: "a.b.c.d/22", Output format: a.b.c.d/22, e.f.g.h/28"
* tfdoc
Co-authored-by: Ludovico Magnocavallo <ludomagno@google.com>
* Add ip_range variable for apigee-x-instance module
* Add variable definition and validation for ip_range
* Update the validation rule for ip_range variable
- Upgrade to latest terraform version (1.0.4)
- Remove tflint from linting pipeline (was not doing anything)
- Add terraform fmt check to linting pipeline
- Pass all code through terraform fmt
Ludovico Magnocavallo
Natalia Strelkova
Julio Castillo
Simone Ruffilli
Alex Lo
Daniel Strebel
Saurabh Shivgunde