Deployment Manager release notes

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

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.

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

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

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

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.

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

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.

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

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

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.

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