Update dependency @pulumi/gcp to v9 #3840
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pulumi-renovate[bot]](https://avatars.githubusercontent.com/u/21992475?s=80&v=4){kind=small}
pulumi-renovate
bot
added
dependencies
![pulumi-renovate-approve[bot]](https://avatars.githubusercontent.com/u/21992475?s=60&v=4){kind=small}
Does the PR have any schema changes?Looking good! No breaking changes found. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3840 +/- ##
=======================================
Coverage 42.50% 42.50%
=======================================
Files 86 86
Lines 12622 12622
=======================================
Hits 5365 5365
Misses 6861 6861
Partials 396 396 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
pulumi-renovate
bot
force-pushed
the
renovate/major-pulumi
branch
2 times, most recently
from
9828227 to
a62d7f9
Compare
pulumi-renovate
bot
force-pushed
the
renovate/major-pulumi
branch
from
a62d7f9 to
f1ae910
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.41.1->9.3.0Release Notes
pulumi/pulumi-gcp (@pulumi/gcp)
v9.3.0Compare Source
Does the PR have any schema changes?
Found 9 breaking changes:
Resources
🟢"gcp:compute/vPNTunnel:VPNTunnel": required: "sharedSecret" property is no longer Required🟢"gcp:networksecurity/mirroringEndpointGroup:MirroringEndpointGroup": required: "mirroringDeploymentGroup" property is no longer RequiredTypes
🟢"livenessProbes" property has changed to Required🟢"startupProbes" property has changed to Required🟢"gcp:compute/WireGroupWireProperties:WireGroupWireProperties": required: "bandwidthAllocation" property has changed to Required🟡"gcp:netapp/VolumeHybridReplicationParameters:VolumeHybridReplicationParameters": properties: "peerIpAddresses" type changed from "string" to "array":🟡items had no type but now has &{Type:string Ref: AdditionalProperties: Items: OneOf:[] Discriminator: Plain:false}🟢"gcp:privilegedaccessmanager/getEntitlementApprovalWorkflowManualApprovalStep:getEntitlementApprovalWorkflowManualApprovalStep": required: "id" property has changed to Required🟢"gcp:sql/getDatabaseInstancesInstance:getDatabaseInstancesInstance": required: "pointInTimeRestoreContexts" property has changed to RequiredNew resources:
apigee/apiDeployment.ApiDeploymentdiscoveryengine/dataConnector.DataConnectorkms/organizationKajPolicyConfig.OrganizationKajPolicyConfigsaasruntime/rolloutKind.RolloutKindNew functions:
artifactregistry/getMavenArtifacts.getMavenArtifactsartifactregistry/getNpmPackages.getNpmPackagesWhat's Changed
Full Changelog: pulumi/pulumi-gcp@v9.2.0...v9.3.0
v9.2.0Compare Source
Does the PR have any schema changes?
Looking good! No breaking changes found.
No new resources/functions.
What's Changed
Full Changelog: pulumi/pulumi-gcp@v9.1.0...v9.2.0
v9.1.0Compare Source
What's Changed
Full Changelog: pulumi/pulumi-gcp@v9.0.0...v9.1.0
v9.0.0Compare Source
Pulumi GCP Provider Version Upgrade Guide
Version 9.0.0 of the GCP provider for Pulumi is a major release and includes changes that you need to consider when upgrading.
This guide will help with that process and focuses only on changes from version 8.x to version 9.0.0.
See the Version 8 Upgrade Guide for information on upgrading from 7.x to version 8.0.0.
Breaking changes
GCP provider v9.0 includes several breaking changes to a few resources and invokes. Here are the details:
Resource
gcp.alloydb.Cluster:deletionProtectionhas been added with a default value oftrue. This field destroying or recreating the cluster duringpulumi up. In 9.0.0, existing clusters will havedeletionProtectionset to true during the next refresh unless otherwise set in the program configuration.Resource
gcp.apigee.KeystoresAliasesKeyCertFile:certsInfois no longer an input and instead is only available as an output property.Resource
gcp.artifactregistry.Repository:Resource
gcp.beyondcorp.Applicationremoved:ApplicationIamBinding,ApplicationIamMember, andApplicationIamPolicyhave also been removed.gcp.beyondcorp.SecurityGatewayApplicationinstead.Resource
gcp.bigquery.Table:view.useLegacySqlNo longer has a default value oftrue. You may need to explicitly set this field in your program configuration.Resource
gcp.bigtable.TableIamBinding:instanceis now removed in favor ofinstanceName.Resource
gcp.bigtable.TableIamMember:instanceis now removed in favor ofinstanceName.Resource
gcp.bigtable.TableIamPolicy:instanceis now removed in favor ofinstanceName.Resource
gcp.cloudfunctionsv2.Function:Field
eventTrigger.eventTypeis now a required field.Field
serviceConfig.serviceis now only available as an output property. Remove it from your program configuration when upgrading.Resource
gcp.cloudrunv2.WorkerPool:template.containers.dependsOnis removed.Resource
gcp.colab.RuntimeTemplate:postStartupScriptConfigis removed.Resource
gcp.compute.InstanceTemplate:disks.diskType,disks.mode,disks.interfaceno longer use provider defaults and instead will be set by the API. See the API documentation for more details.Resource
gcp.compute.RegionInstanceTemplate:disks.diskType,disks.mode,disks.interfaceno longer use provider defaults and instead will be set by the API. See the API documentation for more details.Resource
gcp.compute.Subnetwork:enableFlowLogshas been removed in favor oflogConfig.Resource
gcp.gkehub.Membership:descriptionhas been removed.Resource
gcp.gkehub.FeatureMembership:configmanagement.binauthzhas been removed.Resource
gcp.memorystore.Instance:allowFewerZonesDeploymenthas been removed.Resource
gcp.networkservices.LbTrafficExtension:loadBalancingSchemeis now required. It was already needed for this resource to function correctly so no changes should be necessary.Resource
gcp.notebooks.Locationis removed because it was not a functional resource.Resource
gcp.projects.Service:disableOnDestroyno longer defaults totrue.Resource
gcp.redis.Cluster:allowFewerZonesDeploymenthas been removed.Resource
gcp.securesourcemanager.Instance:deletionPolicyhas had its default value changed toPREVENT.Resource
gcp.storage.TransferJob:Several
pathfields have improved validation and now are required to not start with/.Resource
gcp.storage.Bucket:retentionPeriodhas had its type changed tostring.Resource
gcp.storage.Notification:topicnow requires a new format and must be provided in the formatprojects/{{project}}/topics/{{topic}}.Resource
gcp.tpu.Nodehas been removed in favor ofgcp.tpu.V2Vm. For moving from TPU Node to TPU VM architecture, see https://cloud.google.com/tpu/docs/system-architecture-tpu-vm#from-tpu-node-to-tpu-vm.Resource
gcp.vertex.AiIndex:metadataandmetadata.configare now required. These fields were already required for resource functionality, so no change is necessary to existing configurations.Bucket Label Import
In v9, we are removing a patch that changed the Import behavior on
gcp.storage.Bucket.This patch allowed for a
pulumi importto directly import cloud labels to the Bucket'slabelsfield.Going forward, the Import behavior for labels will be on par with all other resources: on a fresh import, the labels will be written to the output-only
effectiveLabelsfield in the Pulumi state, and not to the bucket'slabels.The generated code will not include
labels.To bring Bucket labels under Pulumi management after an import, you now need to explicitly set them on the Bucket's
labelsfield.You may discover any such potential labels from the Bucket's
effectiveLabelsfield.Read more about label handling here.
This change is a bug fix for https://github.com/pulumi/pulumi-gcp/issues/3337.
New Contributors
Full Changelog: pulumi/pulumi-gcp@v8.41.1...v9.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - Monday through Friday ( * * * * 1-5 ) (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.