Closed mbaroody closed 5 years ago
Thank you for your feedback, our team hear you loud and clear. We are working together with the documentation team to improve the usability and remove the ambiguity around the types and their properties used in Deployment Manager.
Let me try to explain what is happening here:
Some of the GCP APIs working really well, "out of the box" with the Deployment manager engine. For example: gcp-types/compute-v1:firewalls. This means the dicovery document of the API is used as it is, without any input mapping or other overwrites. This also means the API documentations is a good source.
There are APIs which working a bit differently. For example one of the parameter is in the API path and not in the request body. In this case, input mapping may be needed. You can read more about input mapping in the custom type provider section.
It is not always obvious what changes and why got applied and currently the best source is the 'examples/v2' and 'google/resource-snippets' folders. Soon there will be additional information about custom behaviour of the types.
Last but not least, please take a look at the CloudFoundation Toolkit implementation, it may saves you a lots of time as well. ( Currently we are pushing major updates to the new repo.)
I am trying to create a GKE cluster with Deployment Manager using the following as a reference: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.zones.clusters. I know this differs from the examples in this repository slightly. I used the documentation instead of the examples because the examples use fields that are listed as deprecated. Here is my template:
When I try to create a deployment, I get the following error:
This leads me to believe that the examples are the source of truth and not the documentation. Can someone help me figure out what I'm doing wrong?