Added support for Cloud Scheduler through gcp-types/cloudscheduler-v1:projects.locations.jobs.

Fixed

Deployment Manager now correctly deletes Compute Engine forwarding rules of type compute.v1.forwardingRule, compute.beta.forwardingRule, gcp-types/compute-v1:forwardingRules and gcp-types/compute-beta:forwardingRules when the resource name does not match the forwarding rule name.

Change

Updates on Cloud Functions resources using gcp-types/cloudfunctions-v1 now retry on 429 errors.

Change

Performance improvements when handling large Swagger / OpenAPI specs when adding an API as a type provider.

Fixed

Deployment Manager now acquires existing GKE cluster resources of type gcp-types/container-v1:projects.locations.clusters.

Change

You can now apply granular IAM Permissions to the Google APIs service account used by Deployment Manager, as we've removed the requirement for roles/editor being assigned to the service account.

Change

GKE clusters and node pools will wait for maintenance to complete before attempting to apply any updates. Affected collections:

• gcp-types/container-v1:projects.zones.clusters
• gcp-types/container-v1:projects.locations.clusters
• gcp-types/container-v1:projects.zones.clusters.nodePools
• gcp-types/container-v1:projects.locations.clusters.nodePools
• gcp-types/container-v1beta1:projects.zones.clusters
• gcp-types/container-v1beta1:projects.locations.clusters
• gcp-types/container-v1beta1:projects.zones.clusters.nodePools
• gcp-types/container-v1beta1:projects.locations.clusters.nodePools

Fixed

Deployment Manager now correctly acquires Access Context Manager resources of type gcp-types/accesscontextmanager-v1:accessPolicies.accessLevels and gcp-types/accesscontextmanager-v1beta:accessPolicies.accessLevels if the resources already exist.

Change

Added support for updating Cloud Pub/Sub subscriptions using gcp-types/pubsub-v1:projects.subscriptions.

Change

Added support for updating the following properties on gcp-types/container-v1:projects.zones.clusters and gcp-types/container-v1:projects.locations.clusters:

• binaryAuthorization
• databaseEncryption
• masterAuthorizedNetworksConfig
• autoscaling
• resourceUsageExportConfig
• verticalPodAutoscaling

Additionally, for gcp-types/container-v1beta1:projects.zones.clusters and gcp-types/container-v1beta1:projects.locations.clusters the following fields can also be updated:

• podSecurityPolicyConfig
• privateClusterConfig
• shieldedNodes
• workloadIdentityConfig

Fixed

Deployment Manager now correctly updates autoscaling properties for resources of type gcp-types/container-v1:projects.locations.clusters.nodePools and gcp-types/container-v1beta1:projects.locations.clusters.nodePools.

If your Python templates use features that are only for Python 2.x, your templates will now continue to work until June 2020.

Learn about migrating your templates to Python 3.

Deployment Manager now supports templates written in Python 3.

The Python community announced that it will sunset Python 2 on January 1, 2020, and is encouraging all developers to upgrade to Python 3 as soon as they can.

We recommend that you make sure that your Python templates are compatible with Python 3 as soon as possible.

When you're creating your deployments, we recommend using the production-ready templates from the Cloud Foundation Toolkit. The templates use Google Cloud's best practices for managing resources.

See the list of sample templates.

You can now use the gcp-types/compute-v1:externalVpnGateways type to create Compute Engine v1 ExternalVpnGateway resources.

Feature

You can now use the gcp-types/compute-v1:vpnGateways type to create Compute Engine v1 VpnGateway resources.

The walkthrough of Deployment Manager's best practices has been updated, with an optional interactive version that runs in Cloud Shell.

Try the interactive version here:

Open in Cloud Shell

You can now use the gcp-types/cloudresourcemanager-v1 type provider to create IAM mappings for projects and organizations.

For a list of supported type providers, see Supported GCP type providers.

In type providers, the input mappings for header fields are now applied to getting long-running operations.

For information on creating custom type providers, read the guidelines for creating a type provider.

Feature

You can now use Deployment Manager to update labels for Cloud Pub/Sub resources.

If you are using the Deployment Manager API, read the guidelines for managing long-running operations.

Added support for Redis v1 API using the type-provider gcp-types/redis-v1.

Feature

Deployment Manager templates can be used in Private Catalog.

Added support for Cloud DNS v1 RecordSets using the type-provider gcp-types/dns-v1:resourceRecordSets.

Feature

Added a new template environment variable, username, which you can use in Python templates using context.env["username"], and in Jinja templates using env["username"].

For information on using environment variables in templates, see Using environment variables.

Feature

Added support for Access Context Manager v1beta using the type provider gcp-types/accesscontextmanager-v1beta.

For a list of supported type providers, see Supported GCP type providers.

Expanded support for creating and acquiring project folders using the type-provider gcp-types/cloudresourcemanager-v2:folders.

For a list of supported type providers, see Supported GCP type providers.

Added glob import support to gcloud. You can import templates using wildcards in template paths.

For the syntax to enable glob imports, see the SDK release notes.

When you are creating or updating deployments, you can select a CREATE policy for new resources. This ensures that if a resource you are trying to create already exists in the project, the deployment fails.

For information on policies for creating resources, see Setting policies for creating resources.

The appengine.v1beta4 and appengine.v1beta5 resource types are no longer supported.

Feature

Updated the gcloud tool so that you can create deployments directly with composite types. Also added new --template flag to support creating deployments with templates.

Added support for labels on deployments.

Added new returnValues query parameter for the variables().list method to return values for variables that the caller has runtimeconfig.variables.get permission on.

Added new project_number environment variable.

Added new Type Registry feature that allows users to add composite types and add third-party APIs as type providers. This feature is in Beta.

Runtime Configurator updates: * Converted gcloud commands so that the command group is now under runtime-config * Updated gcloud commands to the gcloud beta component.

Added support to the gcloud command-line tool for creating plaintext variable values.

Updated gcloud command-line tool syntax so that the --properties flag now accepts key:value pairs. The old syntax, key=value, will still work but users should transition to using the new syntax. For more information, read Specifying template properties on the command-line.

Added documentation on configuring Deployment Manager to use images from another project.

Runtime Configurator updates:

• Added support for plaintext variable values when creating a variable in the API. This is not yet supported with the gcloud command-line tool.
• Added optional requestId field for create() requests to ensure that requests are unique.

Added support for specifying IAM policies in your configurations. Read the documentation for more information.

Published a Syntax Reference that describes the syntax of Deployment Manager.

Added support for predefined Deployment Manager IAM roles in Beta.

Updated resource quotas for Runtime Configurator so that it is now based on amount of data per user instead of the number of resources. The default quota is 4 MB of data per user. Also, updated quota for API requests.

Feature

Removed the 4 KB limit on variable values for Runtime Configurator.

Added support for hosting templates externally on Google Cloud Storage or on another publicly-accessible URL. Read Hosting Templates Externally for more information.

Added support for outputs so you can expose key properties of your configuration for others to use.