Skip to content

fix(deps): update module github.com/ibm/vpc-go-sdk to v0.87.1#657

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-ibm-vpc-go-sdk-0.x
Open

fix(deps): update module github.com/ibm/vpc-go-sdk to v0.87.1#657
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github.com-ibm-vpc-go-sdk-0.x

Conversation

@renovate

@renovate renovate Bot commented Apr 27, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/IBM/vpc-go-sdk v0.69.1v0.87.1 age confidence

Release Notes

IBM/vpc-go-sdk (github.com/IBM/vpc-go-sdk)

v0.87.1

Compare Source

What's Changed


unmarshalinstancetemplate supports threads_per_core

v0.87.0

Compare Source

What's Changed

API Version Bump

  • Default API version updated from 2026-06-162026-06-23.

New Features

Instance – Software Attachments

New support for managing software attachments on virtual server instances. Three new API operations allow you to list, get, and update software attachments on an instance.

New API operations:

Method Description
ListInstanceSoftwareAttachments List all software attachments for an instance
GetInstanceSoftwareAttachment Retrieve a specific software attachment
UpdateInstanceSoftwareAttachment Update (patch) a software attachment

New types added:

Type Description
InstanceSoftwareAttachment Full representation of a software attachment on an instance
InstanceSoftwareAttachmentCatalogOffering The catalog offering associated with the software attachment
InstanceSoftwareAttachmentCollection Collection wrapper for listing software attachments
InstanceSoftwareAttachmentEntitlement Entitlement info for the software (includes licensed software list)
InstanceSoftwareAttachmentEntitlementLicensedSoftware A single licensed software entry in the entitlement
InstanceSoftwareAttachmentEntitlementLicensedSoftwareVendor Vendor information for licensed software
InstanceSoftwareAttachmentLifecycleReason A reason code + message describing the current lifecycle state
InstanceSoftwareAttachmentOfferingInstance The offering instance associated with this attachment
InstanceSoftwareAttachmentPatch Patch payload for updating a software attachment
InstanceSoftwareAttachmentReference A reference to a software attachment (used from Instance)

New options types:

Type Description
GetInstanceSoftwareAttachmentOptions Options for GetInstanceSoftwareAttachment
ListInstanceSoftwareAttachmentsOptions Options for ListInstanceSoftwareAttachments
UpdateInstanceSoftwareAttachmentOptions Options for UpdateInstanceSoftwareAttachment

New lifecycle state constants (InstanceSoftwareAttachment.LifecycleState):

  • deleting, failed, pending, stable, suspended, updating, waiting

New lifecycle reason code constants (InstanceSoftwareAttachmentLifecycleReason.Code):

  • failed_licensing, failed_registration, internal_error, pending_registration

Updated structs:

  • Instance – added SoftwareAttachments []InstanceSoftwareAttachmentReference field.

Instance – Threads Per Core

New support for configuring the number of threads per core for virtual server instances.

Updated structs:

  • Instance – added ThreadsPerCore *int64 (the current threads per core for the instance).
  • InstancePatch – added ThreadsPerCore *int64 (patchable; instance must be stopping or stopped).
  • InstancePrototype – added ThreadsPerCore *int64 (set at creation; defaults to profile value if unspecified).
  • InstanceTemplate – added ThreadsPerCore *int64.
  • InstanceTemplatePrototype – added ThreadsPerCore *int64.

Instance Profile – New Enum Descriptors

Two new profile capability descriptors for vCPU count and threads per core:

New types added:

Type Description
InstanceProfileSupportedVcpuCountEnum Enumerated supported vCPU counts for a profile (type: "enum", values []int64)
InstanceProfileThreadsPerCoreEnum Enumerated supported threads-per-core values for a profile (type: "enum", default *int64, values []int64)

Updated struct: InstanceProfile – updated fields:

  • SupportedVcpuCount changed to *InstanceProfileSupportedVcpuCountEnum.
  • ThreadsPerCore changed to *InstanceProfileThreadsPerCoreEnum.

Instance Lifecycle Reason – New Code
  • InstanceLifecycleReasonCodeFailedLicensingConst = "failed_licensing" added to InstanceLifecycleReason.Code — indicates that allocation of one or more software licenses has failed.

Load Balancer – mTLS Support

New mutual TLS (mTLS) support for load balancer listeners and pools, gated by a new mtls_supported flag on the load balancer and its profile.

New types added:

Type Description
LoadBalancerListenerClientAuthentication Client auth config present on an existing listener
LoadBalancerListenerClientAuthenticationPatch Patch payload to update listener client authentication
LoadBalancerListenerClientAuthenticationPrototype Prototype for setting client auth when creating a listener; constructor: NewLoadBalancerListenerClientAuthenticationPrototype
LoadBalancerListenerClientAuthenticationCertificateAuthorityPatch Base discriminated type for patching the CA on listener client auth
LoadBalancerListenerClientAuthenticationCertificateAuthorityPatchByCRN CRN-keyed variant; constructor: NewLoadBalancerListenerClientAuthenticationCertificateAuthorityPatchByCRN
LoadBalancerPoolClientAuthentication Client auth config present on an existing pool
LoadBalancerPoolClientAuthenticationPatch Patch payload to update pool client authentication
LoadBalancerPoolClientAuthenticationPrototype Prototype for setting client auth when creating a pool; constructor: NewLoadBalancerPoolClientAuthenticationPrototype
LoadBalancerPoolServerAuthentication Server authentication config present on an existing pool (absent if pool.protocol != https)
LoadBalancerPoolServerAuthenticationPatch Patch payload to update pool server authentication
LoadBalancerPoolServerAuthenticationPrototype Prototype for setting server auth when creating a pool
LoadBalancerProfileMtlsSupported Base type indicating mTLS support on a profile
LoadBalancerProfileMtlsSupportedFixed Fixed-value variant (type: "fixed")
LoadBalancerProfileMtlsSupportedDependent Dependent-on-config variant (type: "dependent")

Updated structs:

  • LoadBalancer – added MtlsSupported *bool.
  • LoadBalancerListener – added ClientAuthentication *LoadBalancerListenerClientAuthentication.
  • LoadBalancerListenerPatch – added ClientAuthentication *LoadBalancerListenerClientAuthenticationPatch (set null to remove).
  • LoadBalancerListenerPrototypeLoadBalancerContext – added ClientAuthentication *LoadBalancerListenerClientAuthenticationPrototype.
  • CreateLoadBalancerListenerOptions – added ClientAuthentication field + SetClientAuthentication setter.
  • LoadBalancerPool – added ClientAuthentication *LoadBalancerPoolClientAuthentication and ServerAuthentication *LoadBalancerPoolServerAuthentication.
  • LoadBalancerPoolPatch – added ClientAuthentication *LoadBalancerPoolClientAuthenticationPatch and ServerAuthentication *LoadBalancerPoolServerAuthenticationPatch (set null to remove each).
  • LoadBalancerPoolPrototypeLoadBalancerContext – added ClientAuthentication and ServerAuthentication prototype fields.
  • CreateLoadBalancerPoolOptions – added ClientAuthentication + ServerAuthentication fields and their respective setters.
  • LoadBalancerProfile – added MtlsSupported LoadBalancerProfileMtlsSupportedIntf.

v0.86.0

Compare Source

What's Changed

API Version Bump

  • Default API version updated from 2026-06-09 -> 2026-06-16.

New Features

Load Balancer - Advanced Health Checks

New support for advanced HTTP/HTTPS health check configuration on load balancer pools. This feature is gated by the new advanced_health_checks_supported flag on the load balancer and its profile.

New types added:

Type Description
LoadBalancerPoolHealthMonitorTypeHttphttpsRequest HTTP request config (body, headers, method) used for health checks
LoadBalancerPoolHealthMonitorTypeHttphttpsRequestHeader A single HTTP request header (field + value) for health checks
LoadBalancerPoolHealthMonitorTypeHttphttpsRequestHeaderPrototype Prototype for creating a request header
LoadBalancerPoolHealthMonitorTypeHttphttpsRequestPatch Patch type to update HTTP request config on a health monitor
LoadBalancerPoolHealthMonitorTypeHttphttpsRequestPrototype Prototype (discriminated union) for setting request config when creating a health monitor
LoadBalancerPoolHealthMonitorTypeHttphttpsRequestPrototypeLoadBalancerPoolHealthMonitorTypeHttphttpsRequestGetPrototype GET-method variant of the request prototype
LoadBalancerPoolHealthMonitorTypeHttphttpsRequestPrototypeLoadBalancerPoolHealthMonitorTypeHttphttpsRequestPostPrototype POST-method variant of the request prototype
LoadBalancerPoolHealthMonitorTypeHttphttpsResponse HTTP response config (status codes, body regex) for health checks
LoadBalancerPoolHealthMonitorTypeHttphttpsResponsePatch Patch type to update HTTP response config on a health monitor
LoadBalancerPoolHealthMonitorTypeHttphttpsResponsePrototype Prototype for setting response config when creating a health monitor

Updated structs:

  • LoadBalancerPoolHealthMonitor - added optional Request and Response fields.
  • LoadBalancerPoolHealthMonitorPatch - added optional Request and Response patch fields.
  • LoadBalancerPoolHealthMonitorPrototype - added optional Request and Response prototype fields.

Load Balancer - FQDN Pool Members

New support for specifying pool members by their fully qualified domain name (FQDN), gated by the new fqdn_pool_members_supported flag.

New types added:

Type Description
LoadBalancerPoolMemberTargetFqdn Represents a pool member target identified by FQDN
LoadBalancerPoolMemberTargetPrototypeFqdn Prototype for creating a pool member target using an FQDN; constructor: NewLoadBalancerPoolMemberTargetPrototypeFqdn

Updated structs:

  • LoadBalancerPoolMemberTarget - added Fqdn field; added LoadBalancerPoolMemberTargetFqdn to the list of discriminator variants.
  • LoadBalancerPoolMemberTargetPrototype - added Fqdn field; added LoadBalancerPoolMemberTargetPrototypeFqdn variant.

Load Balancer - New Profile Capability Fields

Two new profile-level capability descriptors with fixed / dependent discriminated subtypes:

Type Description
LoadBalancerProfileAdvancedHealthCheckSupported Indicates whether advanced health checks are supported (base)
LoadBalancerProfileAdvancedHealthCheckSupportedFixed Fixed value variant
LoadBalancerProfileAdvancedHealthCheckSupportedDependent Dependent-on-config variant
LoadBalancerProfileFqdnSupported Indicates whether FQDN pool members are supported (base)
LoadBalancerProfileFqdnSupportedFixed Fixed value variant
LoadBalancerProfileFqdnSupportedDependent Dependent-on-config variant

Updated struct: LoadBalancerProfile - added fields:

  • AdvancedHealthChecksSupported (LoadBalancerProfileAdvancedHealthCheckSupportedIntf)
  • FqdnPoolMembersSupported (LoadBalancerProfileFqdnSupportedIntf)

Updated struct: LoadBalancer - added fields:

  • AdvancedHealthChecksSupported *bool - indicates whether this load balancer supports advanced health checks.
  • FqdnPoolMembersSupported *bool - indicates whether this load balancer supports FQDN-based pool members.

Load Balancer - starts_with Condition for Listener Policy Rules

A new starts_with condition constant has been added to listener policy rules:

  • CreateLoadBalancerListenerPolicyRuleOptionsConditionStartsWithConst = "starts_with"
  • LoadBalancerListenerPolicyRuleConditionStartsWithConst = "starts_with"
  • LoadBalancerListenerPolicyRulePatchConditionStartsWithConst = "starts_with"
  • LoadBalancerListenerPolicyRulePrototypeConditionStartsWithConst = "starts_with"

Load Balancer Pool - If-Match Header on Update

UpdateLoadBalancerPoolWithContext now supports optimistic concurrency control via the If-Match header:

  • UpdateLoadBalancerPoolOptions has a new IfMatch *string field.
  • New setter: SetIfMatch(ifMatch string).
  • If provided, the header If-Match: <etag> is included in the outbound PATCH request.

Documentation / Clarifications

  • BareMetalServerInitializationPrototype.Keys: Doc updated - Windows images now explicitly require at least one SSH key of type rsa.
  • BareMetalServerInitializationPrototype.UserData: Doc updated to include a link to IBM Cloud user-data documentation.

v0.85.0

Compare Source

What's Changed

BackupPolicyJobReference struct (new)

A new model BackupPolicyJobReference has been introduced to represent a reference to a backup policy job. It carries the following fields:

Field Type Required Description
Deleted *Deleted No Present when the referenced resource has been deleted.
Href *string Yes URL for this backup policy job.
ID *string Yes Unique identifier for this backup policy job.
ResourceType *string Yes Resource type; always "backup_policy_job".

An associated constant BackupPolicyJobReferenceResourceTypeBackupPolicyJobConst and an unmarshaller UnmarshalBackupPolicyJobReference have also been added.


SnapshotConsistencyGroup.BackupPolicyJob field (new)

The SnapshotConsistencyGroup struct now includes an optional BackupPolicyJob *BackupPolicyJobReference field. When present, it identifies the backup policy job that created the snapshot consistency group. Snapshot consistency groups sharing the same backup policy job identifier represent snapshots of the same instance taken across different storage generations.


ListSnapshotConsistencyGroupsOptions.BackupPolicyJobID filter (new)

A new filter field BackupPolicyJobID *string has been added to ListSnapshotConsistencyGroupsOptions, allowing callers to filter the snapshot consistency groups collection by backup_policy_job.id.

A corresponding setter SetBackupPolicyJobID has been added:

options.SetBackupPolicyJobID("r006-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx")

The query parameter is propagated in ListSnapshotConsistencyGroupsWithContext via backup_policy_job.id.


Changes

API version bumped to 2026-06-09

The default API version string used by the client has been updated from 2026-06-02 to 2026-06-09:


Backup policy instance type — multi-generation clarification

The documentation comments for BackupPolicyPrototypeBackupPolicyMatchResourceTypeInstancePrototype.MatchResourceType have been updated to clarify multi-storage-generation behaviour:


Snapshot consistency group prototype — storage_generation constraint relaxed

The documentation comments for the Snapshots field on both SnapshotConsistencyGroupPrototype and SnapshotConsistencyGroupPrototypeSnapshotConsistencyGroupBySnapshots have been updated:


Breaking Changes

None.


Bug Fixes

None.

v0.84.0

Compare Source

What's Changed

API Version
  • Updated from 2026-04-07 to 2026-06-02
Breaking Changes
IKE Policy - Multiple Algorithm Support
  • Constructor changed: NewCreateIkePolicyOptions(ikeVersion) now requires only ikeVersion
  • Deprecated fields (use array versions instead):
    • AuthenticationAlgorithmAuthenticationAlgorithms
    • DhGroupDhGroups
    • EncryptionAlgorithmEncryptionAlgorithms
  • Algorithm arrays support priority-based negotiation (first = highest priority)
  • IKE v1 requires exactly one algorithm per array
IPsec Policy - Multiple Algorithm Support
  • Deprecated fields (use array versions instead):
    • AuthenticationAlgorithmAuthenticationAlgorithms
    • EncryptionAlgorithmEncryptionAlgorithms
    • PfsPfsGroups
  • New multiple enum value indicates multi-algorithm support
Share Access Control
  • Deprecated: vpc access control mode → Use security_group instead
New Features
  • VPN Policies: Support for multiple algorithms with priority-based negotiation
  • Volume Capacity: Storage Gen 2 now supports up to 32,000 GB (Gen 1 remains 250 GB)
  • Default Volume Capacity: System images default to 100 GB or image minimum (whichever is larger)
Migration Examples
// IKE Policy - Old (deprecated)
options := vpcService.NewCreateIkePolicyOptions("sha256", 14, "aes256", 2)

// IKE Policy - New (recommended)
options := vpcService.NewCreateIkePolicyOptions(2)
options.SetAuthenticationAlgorithms([]string{"sha256", "sha384"})
options.SetDhGroups([]int64{14, 15})
options.SetEncryptionAlgorithms([]string{"aes256", "aes192"})

// IPsec Policy - Old (deprecated)
options.SetAuthenticationAlgorithm("sha256")
options.SetPfs("group_14")

// IPsec Policy - New (recommended)
options.SetAuthenticationAlgorithms([]string{"sha256", "sha384"})
options.SetPfsGroups([]string{"group_14", "group_15"})

// Share - Old (deprecated)
sharePrototype.SetAccessControlMode("vpc")

// Share - New (recommended)
sharePrototype.SetAccessControlMode("security_group")
Notes
  • Deprecated fields continue to work but will be removed in future releases
  • Combined-mode encryption (aes*gcm16) requires authentication_algorithms: ["disabled"]

v0.83.2

Compare Source

Image Partial Availability, Zones Support

API Version Update

  • Updated default API version from 2026-04-07 to 2026-04-14

Image Resource Enhancements

New zones Property

Added support for the zones property in the Image resource, which indicates the zones where an image is available for use:

  • When image status is available or deprecated: includes all zones in the region
  • When image status is partially_available: includes one or more zones in the region
  • When image status is failed, obsolete, pending, unusable, or deleting: array is empty
New Image Status: partially_available

Added new status constant ImageStatusPartiallyAvailableConst to support images that are available in some zones but not all zones in a region.

Updated Image Status Documentation

Improved documentation formatting for image status values:

  • available: image can be used to create resources
  • deleting: image is being deleted, and can no longer be used to create resources
  • deprecated: image is slated to be deleted, but can still be used to create resources
  • failed: image was not created successfully, and cannot be used to create resources
  • obsolete: image is slated to be deleted, and can no longer be used to create resources
  • partially_available: image can be used to create resources in the zones listed in the zones property
  • pending: image is being imported, and cannot yet be used to create resources
  • unusable: image cannot be used (see status_reasons[] for possible remediation)
DeleteImage Documentation Update

Simplified the conditions under which an image cannot be deleted:

  • Removed the condition about status of pending with status_reasons code of image_request_in_progress
  • Retained conditions:
    • Image has a status of deleting
    • Image has catalog_offering.managed set to true

Breaking Changes

None. This is a backward-compatible enhancement.

Related Constants

  • ImageStatusPartiallyAvailableConst = "partially_available"
  • ListImagesOptionsStatusPartiallyAvailableConst = "partially_available"

v0.83.1

Compare Source

Image Partial Availability, Zones Support

API Version Update

  • Updated default API version from 2026-04-07 to 2026-04-14

Image Resource Enhancements

New zones Property

Added support for the zones property in the Image resource, which indicates the zones where an image is available for use:

  • When image status is available or deprecated: includes all zones in the region
  • When image status is partially_available: includes one or more zones in the region
  • When image status is failed, obsolete, pending, unusable, or deleting: array is empty
New Image Status: partially_available

Added new status constant ImageStatusPartiallyAvailableConst to support images that are available in some zones but not all zones in a region.

Updated Image Status Documentation

Improved documentation formatting for image status values:

  • available: image can be used to create resources
  • deleting: image is being deleted, and can no longer be used to create resources
  • deprecated: image is slated to be deleted, but can still be used to create resources
  • failed: image was not created successfully, and cannot be used to create resources
  • obsolete: image is slated to be deleted, and can no longer be used to create resources
  • partially_available: image can be used to create resources in the zones listed in the zones property
  • pending: image is being imported, and cannot yet be used to create resources
  • unusable: image cannot be used (see status_reasons[] for possible remediation)
DeleteImage Documentation Update

Simplified the conditions under which an image cannot be deleted:

  • Removed the condition about status of pending with status_reasons code of image_request_in_progress
  • Retained conditions:
    • Image has a status of deleting
    • Image has catalog_offering.managed set to true

Breaking Changes

None. This is a backward-compatible enhancement.

Related Constants

  • ImageStatusPartiallyAvailableConst = "partially_available"
  • ListImagesOptionsStatusPartiallyAvailableConst = "partially_available"

v0.83.0

Compare Source

Image Partial Availability, Zones Support

API Version Update

  • Updated default API version from 2026-04-07 to 2026-04-14

Image Resource Enhancements

New zones Property

Added support for the zones property in the Image resource, which indicates the zones where an image is available for use:

  • When image status is available or deprecated: includes all zones in the region
  • When image status is partially_available: includes one or more zones in the region
  • When image status is failed, obsolete, pending, unusable, or deleting: array is empty
New Image Status: partially_available

Added new status constant ImageStatusPartiallyAvailableConst to support images that are available in some zones but not all zones in a region.

Updated Image Status Documentation

Improved documentation formatting for image status values:

  • available: image can be used to create resources
  • deleting: image is being deleted, and can no longer be used to create resources
  • deprecated: image is slated to be deleted, but can still be used to create resources
  • failed: image was not created successfully, and cannot be used to create resources
  • obsolete: image is slated to be deleted, and can no longer be used to create resources
  • partially_available: image can be used to create resources in the zones listed in the zones property
  • pending: image is being imported, and cannot yet be used to create resources
  • unusable: image cannot be used (see status_reasons[] for possible remediation)
DeleteImage Documentation Update

Simplified the conditions under which an image cannot be deleted:

  • Removed the condition about status of pending with status_reasons code of image_request_in_progress
  • Retained conditions:
    • Image has a status of deleting
    • Image has catalog_offering.managed set to true

Breaking Changes

None. This is a backward-compatible enhancement.

Related Constants

  • ImageStatusPartiallyAvailableConst = "partially_available"
  • ListImagesOptionsStatusPartiallyAvailableConst = "partially_available"

v0.82.1

Compare Source

API Version Update
  • Updated API version from 2026-03-24 to 2026-04-07

New Features

1. Pagination Support for Instance Profiles

Enhancement: Added comprehensive pagination support to the ListInstanceProfiles API endpoint.

Changes:
  • New Query Parameters:

    • start - Server-provided token for pagination cursor
    • limit - Number of resources to return per page
  • Enhanced Response Structure:

    • first - Link to the first page of resources
    • limit - Maximum number of resources per request
    • next - Link to the next page (when available)
    • total_count - Total number of resources across all pages
  • New Pager Implementation:

    • Added InstanceProfilesPager struct for simplified pagination
    • Methods available:
      • NewInstanceProfilesPager() - Create new pager instance
      • HasNext() - Check if more results are available
      • GetNext() - Retrieve next page of results
      • GetNextWithContext() - Retrieve next page with context
      • GetAll() - Retrieve all results across all pages
      • GetAllWithContext() - Retrieve all results with context

2. Zone Information for Instance Profiles

Enhancement: Instance profiles now include zone availability information.

Changes:
  • Added zones field to InstanceProfile struct
  • Type: []ZoneReference (array of zone references)
  • Provides list of zones in the region that support each instance profile

v0.82.0

Compare Source

API Version Update
  • Updated API version from 2026-03-24 to 2026-04-07

New Features

1. Pagination Support for Instance Profiles

Enhancement: Added comprehensive pagination support to the ListInstanceProfiles API endpoint.

Changes:
  • New Query Parameters:

    • start - Server-provided token for pagination cursor
    • limit - Number of resources to return per page
  • Enhanced Response Structure:

    • first - Link to the first page of resources
    • limit - Maximum number of resources per request
    • next - Link to the next page (when available)
    • total_count - Total number of resources across all pages
  • New Pager Implementation:

    • Added InstanceProfilesPager struct for simplified pagination
    • Methods available:
      • NewInstanceProfilesPager() - Create new pager instance
      • HasNext() - Check if more results are available
      • GetNext() - Retrieve next page of results
      • GetNextWithContext() - Retrieve next page with context
      • GetAll() - Retrieve all results across all pages
      • GetAllWithContext() - Retrieve all results with context

2. Zone Information for Instance Profiles

Enhancement: Instance profiles now include zone availability information.

Changes:
  • Added zones field to InstanceProfile struct
  • Type: []ZoneReference (array of zone references)
  • Provides list of zones in the region that support each instance profile

v0.81.1

Compare Source

Volume Jobs Support

Added comprehensive support for volume jobs, enabling asynchronous operations on block storage volumes such as migration between storage tiers.


New API Methods

Volume Job Operations
  • ListVolumeJobs - List all jobs for a volume
  • CreateVolumeJob - Create a new job for a volume
  • GetVolumeJob - Retrieve details of a specific volume job
  • UpdateVolumeJob - Update a volume job
  • DeleteVolumeJob - Delete a volume job
  • CancelVolumeJob - Cancel a running volume job
Context-Aware Variants

All methods include context-aware variants (e.g., ListVolumeJobsWithContext) for better control over request lifecycle.


New Core Models

Volume Job Models
  • VolumeJob - Core volume job resource
  • VolumeJobIntf - Interface for volume job types
  • VolumeJobCollection - Collection of volume jobs with pagination support
  • VolumeJobPatch - Patch model for updating volume jobs
  • VolumeJobStatusReason - Status reason details for job state
Volume Job Prototypes
  • VolumeJobPrototype - Base prototype for creating volume jobs
  • VolumeJobPrototypeIntf - Interface for job prototype types
  • VolumeJobPrototypeVolumeJobTypeMigratePrototype - Prototype for migration jobs
Job Type Specific Models
  • VolumeJobTypeMigrate - Migration job type implementation
  • VolumeJobTypeMigrateParameters - Parameters for volume migration jobs

New Options Structs

  • ListVolumeJobsOptions - Options for listing volume jobs
  • CreateVolumeJobOptions - Options for creating a volume job
  • GetVolumeJobOptions - Options for retrieving a volume job
  • UpdateVolumeJobOptions - Options for updating a volume job
  • DeleteVolumeJobOptions - Options for deleting a volume job
  • CancelVolumeJobOptions - Options for canceling a volume job

Pagination Support

New Pager
  • VolumeJobsPager - Automatic pagination support for listing volume jobs

Job Types

Supported Job Types
  • migrate - Volume migration between storage tiers
    • Constant: VolumeJobPrototypeJobTypeMigrateConst
    • Constant: VolumeJobPrototypeVolumeJobTypeMigratePrototypeJobTypeMigrateConst

Features

  • Full CRUD operations for volume jobs
  • Support for asynchronous volume operations
  • Job status tracking and monitoring
  • Cancellation support for running jobs
  • Pagination support for job listings
  • Type-safe job prototypes with validation
  • Context-aware request handling

v0.81.0

Compare Source

Volume Jobs Support

Added comprehensive support for volume jobs, enabling asynchronous operations on block storage volumes such as migration between storage tiers.


New API Methods

Volume Job Operations
  • ListVolumeJobs - List all jobs for a volume
  • CreateVolumeJob - Create a new job for a volume
  • GetVolumeJob - Retrieve details of a specific volume job
  • UpdateVolumeJob - Update a volume job
  • DeleteVolumeJob - Delete a volume job
  • CancelVolumeJob - Cancel a running volume job
Context-Aware Variants

All methods include context-aware variants (e.g., ListVolumeJobsWithContext) for better control over request lifecycle.


New Core Models

Volume Job Models
  • VolumeJob - Core volume job resource
  • VolumeJobIntf - Interface for volume job types
  • VolumeJobCollection - Collection of volume jobs with pagination support
  • VolumeJobPatch - Patch model for updating volume jobs
  • VolumeJobStatusReason - Status reason details for job state
Volume Job Prototypes
  • VolumeJobPrototype - Base prototype for creating volume jobs
  • VolumeJobPrototypeIntf - Interface for job prototype types
  • VolumeJobPrototypeVolumeJobTypeMigratePrototype - Prototype for migration jobs
Job Type Specific Models
  • VolumeJobTypeMigrate - Migration job type implementation
  • VolumeJobTypeMigrateParameters - Parameters for volume migration jobs

New Options Structs

  • ListVolumeJobsOptions - Options for listing volume jobs
  • CreateVolumeJobOptions - Options for creating a volume job
  • GetVolumeJobOptions - Options for retrieving a volume job
  • UpdateVolumeJobOptions - Options for updating a volume job
  • DeleteVolumeJobOptions - Options for deleting a volume job
  • CancelVolumeJobOptions - Options for canceling a volume job

Pagination Support

New Pager
  • VolumeJobsPager - Automatic pagination support for listing volume jobs

Job Types

Supported Job Types
  • migrate - Volume migration between storage tiers
    • Constant: VolumeJobPrototypeJobTypeMigrateConst
    • Constant: VolumeJobPrototypeVolumeJobTypeMigratePrototypeJobTypeMigrateConst

Features

  • Full CRUD operations for volume jobs
  • Support for asynchronous volume operations
  • Job status tracking and monitoring
  • Cancellation support for running jobs
  • Pagination support for job listings
  • Type-safe job prototypes with validation
  • Context-aware request handling\

Edits:

  • Breaking change : - SecurityGroupRuleRemoteCIDR, SecurityGroupRuleRemoteIP -> SecurityGroupRuleRemoteSecurityGroupRuleCIDR, SecurityGroupRuleRemoteSecurityGroupRuleIP

v0.80.0

Compare Source

What's Changed

  • feat(spec): update the sdk to the api spec version 2026-01-27
  • added support for NetworkBandwidthMode in InstanceProfile

Full Changelog: IBM/vpc-go-sdk@v0.79.0...v0.80.0

v0.79.0

Compare Source

API Version Update

  • Updated default VPC API version from 2025-12-16 to 2026-01-20.

Instance Availability Class

Added support for instance availability classes, enabling spot instances and explicit preemption behavior.

New Core Models
  • InstanceAvailability
  • InstanceAvailabilityPatch
  • InstanceAvailabilityPrototype

Availability Policy Enhancements

Extended instance availability policy to model spot preemption behavior.

Updated / Extended Models
  • InstanceAvailabilityPolicy
  • InstanceAvailabilityPolicyPatch
  • InstanceAvailabilityPolicyPrototype
New Capability
  • Added preemption action:
    • delete
    • stop

Instance, Prototype & Template Updates

Added explicit availability support across all instance surfaces.

Updated Structs
  • Instance (availability required in responses)
  • InstancePatch
  • InstancePrototype
  • InstanceTemplate
  • InstanceTemplatePrototype
  • All InstanceBy* and instance-template context structs

Instance Profile Enhancements

Extended instance profiles to declare availability-class constraints.

New Profile Models
  • InstanceProfileAvailabilityClass
  • InstanceProfileAvailabilityClassEnum
  • InstanceProfileAvailabilityClassFixed
Updated Struct
  • InstanceProfile
    • Added required AvailabilityClass

Instance Listing & Filtering

New Filter
  • availability.class (spot, standard) added to ListInstancesOptions

Lifecycle & Status Updates

  • Added new instance status reason:
    • stopped_by_preemption

v0.78.1

Compare Source

What's Changed

  • Add known issues documentation for vpc-go-sdk
  • fix: enhanced unmarshalling on network ACL and security group rule on 0.78.0 pull/149
Protocol all Replacement

The legacy protocol = all value has been removed starting with 0.77.0

  • In earlier versions, all implicitly meant ICMP + TCP + UDP, as only these protocols were supported.
  • With expanded protocol support, this implicit meaning is no longer safe.

Replacement rules:

  • Use icmp_tcp_udp to preserve the original behavior of all.
  • Use any only when you explicitly intend to allow or deny all IP protocols (0–255).

Important:

  • Do not migrate all to any automatically.
  • For network ACLs, deny + icmp_tcp_udp is not allowed; denying ICMP, TCP, and UDP requires three separate rules.

This change affects security group rules and network ACL rules and requires explicit migration to preserve intent.

v0.78.0

Compare Source

API Version Update

  • Updated default VPC API version from 2025-12-09 to 2025-12-16.

VCPU Policy Model (New Feature)

Introduced first-class, policy-driven VCPU modeling across instances and profiles.

New Core Models
  • InstanceVcpu
  • InstanceVcpuBurst
  • InstanceVcpuPatch
  • InstanceVcpuPrototype
New Profile Models
  • InstanceProfileVcpuBurstLimit
  • InstanceProfileVcpuBurstLimitFixed
  • InstanceProfileVcpuPercentage

Instance & Template Struct Updates

Added explicit vcpu support across all instance creation

Updated Structs
  • InstancePatch
  • InstancePrototype
  • InstanceTemplate
  • InstanceTemplatePrototype
  • All InstanceBy* and instance-template context structs

Instance Profile Enhancements

Extended instance profiles to express CPU policy constraints.

Updated Struct
  • InstanceProfile
    • Added VcpuBurstLimit
    • Added VcpuPercentage

Instance Patch Enhancements

Enabled CPU policy updates on existing instances.

New Capability
  • Support for updating vcpu.percentage via InstanceVcpuPatch
  • Restricted to instances in stopping or stopped state

Placement & Reservation Constraints

Strengthened validation and semantics for placement and reservation affinity.

Behavioral Updates
  • Enforced vcpu.percentage = 100 for:
    • Dedicated host placement
    • Dedicated host group placement
    • Reservation-affinity–restricted configurations
  • Updated placement and reservation affinity model contracts to reflect CPU constraints

Serialization & Validation

  • Added marshal/unmarshal support for all new VCPU models
  • Integrated validation for profile-governed CPU policies

v0.77.0

Compare Source

API Version

  • Default API version updated to 2025-12-09.

Breaking Changes

1. Security Group & Network ACL Rule Protocol Semantics

The legacy protocol = all value has been removed.

Previous behavior (API version 2025-12-08 or earlier)
  • all implicitly meant ICMP + TCP + UDP
New behavior (API version 2025-12-09 or later)
Protocol value Meaning
icmp_tcp_udp Exact semantic replacement for old all
any True any protocol (IP protocol numbers 0–255)

Important

  • Old all must be migrated to icmp_tcp_udp
  • Migrating old rules to any would silently widen network access

This is a breaking change for:

  • Security group rules
  • Network ACL rules
  • Terraform / SDK / IaC configurations

2. Network ACL Action × Protocol Constraints
Allow rules
  • allow + icmp_tcp_udp -> valid
  • allow + any -> valid
  • allow + number_<N> -> valid
Deny rules
  • deny + icmp_tcp_udp -> not allowed
  • deny + any -> valid (blocks protocol numbers 0–255)
  • deny + number_<N> -> valid

Additional constraint

  • A network ACL rule created with icmp_tcp_udp cannot later be updated to deny.

New Features

1. Expanded Protocol Support (Preview / Approved Accounts)

Security group and network ACL rules now support the full IP protocol space.

Supported protocol values include:

  • any
  • icmp_tcp_udp
  • icmp, tcp, udp
  • gre, esp, ah, l2tp, vrrp, sctp, rsvp, ip_in_ip
  • number_<N> for any individual protocol number (0–255)

2. Security Group Rule Names
  • Security group rules now have a name property.
  • Can be specified during rule creation.
  • If omitted, the system assigns a hyphenated random name.
  • Names can be updated after creation.
  • Existing rules (including default VPC security group rules) now have system-assigned names.

Schema & Model Changes

Security Group Rules
  • Added name field to the rule schema.
  • protocol response values now return:
    • icmp_tcp_udp instead of all
    • any when explicitly used
Network ACL Rules
  • Protocol discriminator model expanded.
  • Legacy all protocol removed.
  • New discriminator families added to support:
    • any
    • icmp_tcp_udp
    • individual protocol values

Migration Guidelines

1. Protocol Migration
Old value (≤ 2025-12-08) New value (≥ 2025-12-09)
all icmp_tcp_udp

Do not auto-map all to any.


2. Network ACL Deny Rules Migration

If you previously had:

deny + all

Choose intent explicitly:

Deny all protocols

deny + any

Deny only ICMP, TCP, and UDP

deny + icmp
deny + tcp
deny + udp

There is no single-rule equivalent for deny + icmp_tcp_udp.


3. Security Group Rules Migration
  • Replace protocol = all with protocol = icmp_tcp_udp
  • Optionally assign explicit rule names to avoid system-generated names.

4. IaC / Terraform / SDK Impact
  • Any hardcoded protocol = all will fail validation.

  • State refresh may normalize:

    • all -> icmp_tcp_udp
  • One-time diffs expected due to protocol normalization.


Summary

  • all has been removed and replaced by icmp_tcp_udp (legacy-equivalent) and any (true any).
  • This is a deliberate safety-driven breaking change due to protocol space expansion.
  • Migration must preserve intent to avoid unintended network exposure.

v0.76.5

Compare Source

FIX

  • a patch on 0.76.0 to fix the discriminator issue on v0.76.0
SDK Compatibility Patch - Protocol Handling
  • The SDK was patched to handle additional protocol values introduced in newer API versions, ensuring older SDK releases do not fail when reading security group or network ACL rules created with expanded protocol support.

Full Changelog: IBM/vpc-go-sdk@v0.76.0...v0.76.5

v0.76.4

Compare Source

Fix

  • Fix the discriminator issue on rules for network acl and sg on v0.76.2
  • patch on 0.76.2
SDK Compatibility Patch - Protocol Handling
  • The SDK was patched to handle additional protocol values introduced in newer API versions, ensuring older SDK releases do not fail when reading security group or network ACL rules created with expanded protocol support.

Full Changelog: IBM/vpc-go-sdk@v0.76.2...v0.76.4

v0.76.3

Compare Source

FIX

  • Fixes the discriminator issue on rules
  • a patch on 0.76.1
SDK Compatibility Patch - Protocol Handling
  • The SDK was patched to handle additional protocol values introduced in newer API versions, ensuring older SDK releases do not fail when reading security group or network ACL rules created with expanded protocol support.

Full Changelog: IBM/vpc-go-sdk@v0.76.1...v0.76.3

v0.76.2

Compare Source

API Version Update

  • Updated VPC API version from 2025-11-04 to 2025-11-17.

v0.76.1

Compare Source

What's Changed

  • feat(spec): reverted the sdk to the api spec version 2025-11-04

v0.76.0

Compare Source

Highlights

  • API version bumped to 2025-11-18.

  • DNS Binding Migration

    • Removed allow_dns_resolution_binding.
    • New field: dns_resolution_binding_mode = "disabled" | "primary" | "per_resource_binding".
    • Migration rule: false -> "disabled", true -> "primary/per_resource_binding".
  • Endpoint Gateway Resource Bindings – Added

    • Full CRUD: list, get, create, patch, delete.
    • New models: collection, lifecycle reason, target, prototypes, patches.
  • Endpoint Gateway list/create/update rewritten for new binding mode.

  • DNS sharing rules fully updated to binding-mode semantics.

  • Instance Group Scheduled Action fix: cron_spec / run_at ordering + parsing.

New Features

  • Resource Bindings API with FQDN endpoints, lifecycle info, pagination, and patch support.

  • Methods:

    • List/Get/Create/Update/Delete EndpointGatewayResourceBinding.

DNS Binding Mode Replacement

  • Old boolean removed.
  • New required enum field across all models, options, and patches.
  • Updated filters, queries, patch logic, and unmarshal paths.

DNS Topology Updates

  • Primary-mode exclusivity enforced.
  • Per-resource binding requires hub-VPC + primary gateway.
  • All VPC DNS Resolution Binding rules rewritten.

v0.75.1

Compare Source

Bug Fixes
  • Network ACL & Security Group Rules: Fixed discriminator issue
SDK Compatibility Patch - Protocol Handling
  • The SDK was patched to handle additional protocol values introduced in newer API versions, ensuring older SDK releases do not fail when reading security group or network ACL rules created with expanded protocol support.

Full Changelog: IBM/vpc-go-sdk@v0.75.0...v0.75.1

v0.75.0

Compare Source

Highlights

  • API version bumped to 2025-11-04

  • New region: in-che (India, Chennai) added to service URL map.

  • VPN Gateway: Advertised CIDRs (route mode) :

    • ListVPNGatewayAdvertisedCIDRs
    • AddVPNGatewayAdvertisedCIDR
    • CheckVPNGatewayAdvertisedCIDR
    • RemoveVPNGatewayAdvertisedCIDR
  • VPN Gateway: Service Connections

    • ListVPNGatewayServiceConnections
    • GetVPNGatewayServiceConnection
  • Dynamic Route Mode (BGP) plumbing added across models, patches, and prototypes.

  • Optimistic concurrency for VPN gateway connections via optional If-Match on DELETE and PATCH.

  • Multiple fields tightened from optional → required (potentially breaking).

New Features

VPN Gateway: Advertised CIDRs (Route Mode)
  • Endpoints surfaced with options and models to manage static prefixes advertised by routing protocols:

    • Methods: ListVPNGatewayAdvertisedCIDRs, AddVPNGatewayAdvertisedCIDR, CheckVPNGatewayAdvertisedCIDR, RemoveVPNGatewayAdvertisedCIDR

    • Models/Options:

      • VPNGatewayAdvertisedCIDRCollection
      • ListVPNGatewayAdvertisedCIDRsOptions, AddVPNGatewayAdvertisedCIDROptions, CheckVPNGatewayAdvertisedCIDROptions, RemoveVPNGatewayAdvertisedCIDROptions
VPN Gateway: Service Connections
  • Methods: ListVPNGatewayServiceConnections, GetVPNGatewayServiceConnection
  • Pagination supported on list (start, limit).
  • Options/Models: ListVPNGatewayServiceConnectionsOptions, GetVPNGatewayServiceConnectionOptions, VPNGatewayServiceConnectionCollection, VPNGatewayServiceConnection
Dynamic Route Mode & BGP
  • New structures to represent dynamic route mode configuration and state:

    • Local identity: VPNGatewayConnectionDynamicRouteModeLocal, ...LocalPrototype
    • Peer side: VPNGatewayConnectionDynamicRouteModePeer (+ address/fqdn variants) and ...PeerPrototype
    • Tunnel state & prototypes: VPNGatewayConnectionDynamicRouteModeTunnel, VPNGatewayConnectionTunnel, VPNGatewayConnectionTunnelPrototype
  • VPNGatewayConnectionPatch gains:

    • routing_protocol ("none" | "bgp")
    • tunnels (array of VPNGatewayConnectionTunnel)
  • VPNGatewayConnectionPrototype gains tunnels (array of VPNGatewayConnectionTunnelPrototype)

  • VPNGatewayConnectionPeerPatch gains asn (with restricted-ASN guard in docs)

VPN Gateway Model Extensions
  • VPNGateway now includes:

    • advertised_cidrs (static prefixes to advertise)
    • local_asn (gateway/local ASN)
New Region
  • GetServiceURLForRegion now maps in-che -> https://in-che.iaas.cloud.ibm.com/v1

Enhancements

Concurrency Control on VPN Connections
  • DeleteVPNGatewayConnectionOptions and UpdateVPNGatewayConnectionOptions gain optional IfMatch.

    • SDK sets If-Match header when provided; delete/update will fail on ETag mismatch.
Documentation/Comment Clarifications
  • Primary IP comments for CreateInstanceNetworkInterfaceOptions and NetworkInterfacePrototype reflowed for clarity (no semantic change).
  • InstanceProfileCollection.profiles description clarified (“The virtual server instance profiles.”).

Guide

  1. Use ETags for safer updates

    • For delete/patch on VPN gateway connections,

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Apr 27, 2026

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 14 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.23.4 -> 1.25.0
github.com/IBM/go-sdk-core/v5 v5.20.1 -> v5.21.4
golang.org/x/sync v0.12.0 -> v0.18.0
golang.org/x/term v0.30.0 -> v0.37.0
github.com/gabriel-vasile/mimetype v1.4.8 -> v1.4.11
github.com/go-openapi/errors v0.22.0 -> v0.22.4
github.com/go-openapi/strfmt v0.23.0 -> v0.25.0
github.com/go-playground/validator/v10 v10.26.0 -> v10.28.0
github.com/hashicorp/go-retryablehttp v0.7.7 -> v0.7.8
go.mongodb.org/mongo-driver v1.17.2 -> v1.17.6
golang.org/x/crypto v0.36.0 -> v0.45.0
golang.org/x/net v0.38.0 -> v0.47.0
golang.org/x/sys v0.31.0 -> v0.44.0
golang.org/x/text v0.23.0 -> v0.31.0
sigs.k8s.io/yaml v1.4.0 -> v1.6.0

@renovate
renovate Bot force-pushed the renovate/github.com-ibm-vpc-go-sdk-0.x branch from b3e1e0c to fcfcefa Compare June 4, 2026 13:48
@renovate renovate Bot changed the title fix(deps): update module github.com/ibm/vpc-go-sdk to v0.83.2 fix(deps): update module github.com/ibm/vpc-go-sdk to v0.84.0 Jun 4, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-ibm-vpc-go-sdk-0.x branch from fcfcefa to b854aa8 Compare June 11, 2026 11:37
@renovate renovate Bot changed the title fix(deps): update module github.com/ibm/vpc-go-sdk to v0.84.0 fix(deps): update module github.com/ibm/vpc-go-sdk to v0.85.0 Jun 11, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-ibm-vpc-go-sdk-0.x branch from b854aa8 to 334e964 Compare June 17, 2026 15:00
@renovate renovate Bot changed the title fix(deps): update module github.com/ibm/vpc-go-sdk to v0.85.0 fix(deps): update module github.com/ibm/vpc-go-sdk to v0.86.0 Jun 17, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-ibm-vpc-go-sdk-0.x branch from 334e964 to 9491792 Compare June 30, 2026 16:44
@renovate renovate Bot changed the title fix(deps): update module github.com/ibm/vpc-go-sdk to v0.86.0 fix(deps): update module github.com/ibm/vpc-go-sdk to v0.87.0 Jun 30, 2026
@renovate
renovate Bot force-pushed the renovate/github.com-ibm-vpc-go-sdk-0.x branch from 9491792 to 655b547 Compare July 9, 2026 18:00
@renovate renovate Bot changed the title fix(deps): update module github.com/ibm/vpc-go-sdk to v0.87.0 fix(deps): update module github.com/ibm/vpc-go-sdk to v0.87.1 Jul 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants