google-deployment-manager

Do GCP Deployment Manager templates require a schema file?

流过昼夜 提交于 2021-02-19 07:41:20
问题 Since the templates can store values themselves (in addition to receiving values from the configuration yaml file), is a schema required when we create a template? If not, is the use of the schema just to enforce which values are required, and the type of values that need to be provided to the template? EDIT I'm referring to template schemas, not resource properties schema: https://cloud.google.com/deployment-manager/docs/configuration/templates/using-schemas 回答1: Google Deployment Manager

GCP project creation via deploymentmanager

て烟熏妆下的殇ゞ 提交于 2020-01-24 19:20:06
问题 So im trying to create a project with google cloud deployment manager, Ive structured the setup roughly as below: # Structure Org -> Folder1 -> Seed-Project(Location where I am running deployment manager from) Organization: IAM: -> {Seed-Project-Number}@cloudservices.gserviceaccount.com: - Compute Network Admin - Compute Shared VPC Admin - Organisation Viewer - Project Creator # DeploymentManager Resource: type cloudresourcemanager.v1.project name MyNewProject parent id: '{folder1-id}' type:

GCP project creation via deploymentmanager

ε祈祈猫儿з 提交于 2020-01-24 19:19:52
问题 So im trying to create a project with google cloud deployment manager, Ive structured the setup roughly as below: # Structure Org -> Folder1 -> Seed-Project(Location where I am running deployment manager from) Organization: IAM: -> {Seed-Project-Number}@cloudservices.gserviceaccount.com: - Compute Network Admin - Compute Shared VPC Admin - Organisation Viewer - Project Creator # DeploymentManager Resource: type cloudresourcemanager.v1.project name MyNewProject parent id: '{folder1-id}' type:

GCP project creation via deploymentmanager

本小妞迷上赌 提交于 2020-01-24 19:19:30
问题 So im trying to create a project with google cloud deployment manager, Ive structured the setup roughly as below: # Structure Org -> Folder1 -> Seed-Project(Location where I am running deployment manager from) Organization: IAM: -> {Seed-Project-Number}@cloudservices.gserviceaccount.com: - Compute Network Admin - Compute Shared VPC Admin - Organisation Viewer - Project Creator # DeploymentManager Resource: type cloudresourcemanager.v1.project name MyNewProject parent id: '{folder1-id}' type:

SSL issues with jinja HTTPS load balancer - Google Cloud

梦想的初衷 提交于 2019-12-24 16:30:42
问题 I have been able to deploy this load balancer as a HTTP load balancer, and am now trying to deploy this as a HTTPS load balancer. I am attempting this with .JUNJA and .YAML on Google Cloud. I keep getting the error: Invalid value for field 'resource.sslCertificates[0]': 'www.example.com'. The\\ URL is malformed. resources: - name: web-lb-hc #Create a health check for the backend type: compute.v1.httpsHealthCheck properties: port: 443 requestPath: / - name: web-url-map #Required to map url to

google deployment manager assigning IAM policies at project

心不动则不痛 提交于 2019-12-19 11:53:58
问题 I am using to update a project with IAM policies. in GCP deployment manager's templates, they are using python Jinja file, but I would like to add IAM policy (assign a user/service account some role). Can someone modify the Jinja/ config file and pinpoint how I can modify? https://github.com/GoogleCloudPlatform/deploymentmanager-samples/blob/master/examples/v2/project_creation/config.yaml https://github.com/GoogleCloudPlatform/deploymentmanager-samples/blob/master/examples/v2/project_creation

Deployment Manager update error: Deployment in preview must not have a target with UPDATE

笑着哭i 提交于 2019-12-11 02:57:16
问题 Every time I try to run an update through deployment manager to an existing deployment in preview, I get the error: $ gcloud deployment-manager deployments update abc --config abc.yaml ERROR: (gcloud.deployment-manager.deployments.update) ResponseError: code=400, message=Invalid value for field 'resource.target': ''. Deployment in preview must not have a target with UPDATE However, if I don't use the update on the gcloud command line and go to the console and click 'deploy' the update goes