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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/IBM/vpc-go-sdk	v0.69.1 → v0.83.2

---

Release Notes

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

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, supply the last-seen ETag via IfMatch to avoid lost updates:

   _, err := vpc.UpdateVPNGatewayConnection(
     &vpcv1.UpdateVPNGatewayConnectionOptions{
       VPNGatewayID: core.StringPtr(gwID),
       ID:           core.StringPtr(connID),
       IfMatch:      core.StringPtr(etag),
       VPNGatewayConnectionPatch: map[string]interface{}{
         "routing_protocol": "bgp",
       },
     },
   )

2. Manage advertised CIDRs

   • List/add/check/remove static CIDRs on route-mode gateways:

   // Add a prefix
   _, err := vpc.AddVPNGatewayAdvertisedCIDR(
     vpc.NewAddVPNGatewayAdvertisedCIDROptions(gwID, "10.10.0.0/16"),
   )
   // Verify presence
   _, err = vpc.CheckVPNGatewayAdvertisedCIDR(
     vpc.NewCheckVPNGatewayAdvertisedCIDROptions(gwID, "10.10.0.0/16"),
   )
   // List all
   col, _, _ := vpc.ListVPNGatewayAdvertisedCIDRs(
     vpc.NewListVPNGatewayAdvertisedCIDRsOptions(gwID),
   )

3. Enable dynamic route mode (BGP) tunnels

   • When creating or patching route-mode connections using BGP, supply tunnel IPs and, if needed, peer ASN/IKE identity:

   tunnel := &vpcv1.VPNGatewayConnectionTunnelPrototype{
     NeighborIP:        &vpcv1.IP{Address: core.StringPtr("169.254.0.2")},
     TunnelInterfaceIP: &vpcv1.IP{Address: core.StringPtr("169.254.0.1")},
   }
   proto := &vpcv1.VPNGatewayConnectionPrototype{
     Mode:            core.StringPtr("route"),
     RoutingProtocol: core.StringPtr("bgp"),
     Tunnels:         []vpcv1.VPNGatewayConnectionTunnelPrototype{*tunnel},
   }

SDK Summary (Additions)

• Methods:
  ListVPNGatewayAdvertisedCIDRs, AddVPNGatewayAdvertisedCIDR, CheckVPNGatewayAdvertisedCIDR, RemoveVPNGatewayAdvertisedCIDR, ListVPNGatewayServiceConnections, GetVPNGatewayServiceConnection
• Options:
  ListVPNGatewayAdvertisedCIDRsOptions, AddVPNGatewayAdvertisedCIDROptions, CheckVPNGatewayAdvertisedCIDROptions, RemoveVPNGatewayAdvertisedCIDROptions, ListVPNGatewayServiceConnectionsOptions, GetVPNGatewayServiceConnectionOptions
• Models / Patches / Prototypes:
  VPNGatewayAdvertisedCIDRCollection, dynamic-route models listed above, VPNGateway.advertised_cidrs, VPNGateway.local_asn, VPNGatewayConnectionPatch.routing_protocol, VPNGatewayConnectionPatch.tunnels, VPNGatewayConnectionPeerPatch.asn, VPNGatewayConnectionTunnel(Prototype)

v0.74.2

Compare Source

Bug Fixes

• Network ACL & Security Group Rules: Fixed discriminator issue on v0.74.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.74.1...v0.74.2

v0.74.1

Compare Source

What's Changed

• fix(template): correctly unmarshal InstanceTemplate response by type

v0.74.0

Compare Source

What's Changed : Volume bandwidth QoS and Flex profiles support

Version Update

• API Version: 2025-09-23 → 2025-09-30

Major Changes

Volume Bandwidth QoS Mode Support

• New Field Added: VolumeBandwidthQosMode across all instance models
  • Values: pooled, weighted
  • Must be supported by instance profile's volume_bandwidth_qos_modes

Instance Profile Enhancements

• New Field: VolumeBandwidthQosModes in InstanceProfile struct

Model Updates

• Instance Model: Added VolumeBandwidthQosMode field
• InstancePatch: Added optional field with status restrictions (must be stopping or stopped)
• InstancePrototype/Template: Added optional field with profile validation
• All Instance Variants: Updated with VolumeBandwidthQosMode support across network attachment/interface types

Profile Default Changes

• Default Profile: Changed from bx2-2x8 to bxf-2x8

VCPU Manufacturer Enhancement

• New Value: Added unassigned constant for failed/pending/stopped instances

New Constants Added

For Volume Bandwidth QoS Mode:

• InstanceVolumeBandwidthQosModePooledConst = "pooled"
• InstanceVolumeBandwidthQosModeWeightedConst = "weighted"

For VCPU Manufacturer:

• InstanceVcpuManufacturerUnassignedConst = "unassigned"

Documentation Updates

• Volume bandwidth QoS semantics and profile requirements documented across all affected models
• Instance profile compatibility requirements clarified
• Default profile change policy updated

v0.73.1

Compare Source

Bug Fixes

• Network ACL & Security Group Rules: Fixed discriminator issue on v0.73.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.73.0...v0.73.1

v0.73.0

Compare Source

What's Changed

Version Update

• API Version: 2025-09-17 → 2025-09-23

Major Changes

Load Balancer Pool Member Target Enhancements

• New Model Added: LoadBalancerPoolMemberTargetByReservedIP

  • Represents pool members referencing a subnet reserved IP
  • Properties: id, href, name, address
  • Supports 0.0.0.0 placeholder for deferred address assignment
  • resource_type fixed as subnet_reserved_ip

• Renamed Model:

  • LoadBalancerPoolMemberTargetIP → LoadBalancerPoolMemberTargetIPNotReservedIP
  • Explicitly denotes plain IP members not backed by reserved IPs

• New Prototype Identity: LoadBalancerPoolMemberTargetPrototypeReservedIPIdentity

  • Variants: ByID, ByHref
  • Includes patch helpers for reserved IP references

• New Discriminator Constant:

  • subnet_reserved_ip

Load Balancer Profile Enhancements (LoadBalancerProfile struct)

• New Field: targetable_resource_types

  • Declares resource types a profile can target
  • Supported values: instance, subnet_reserved_ip, load_balancer, ip

• New Struct: LoadBalancerProfileTargetableResourceTypes

  • Properties: type (enum), values (list)
  • Constants added for safe value handling

Breaking Changes

1. Model Rename

   • LoadBalancerPoolMemberTargetIP is now LoadBalancerPoolMemberTargetIPNotReservedIP
   • Applications must update references to use the new model name

2. Target Resource Types

   • Pool members are now validated against profile-supported targetable_resource_types
   • Invalid resource types will be rejected

New Constants Added

For Pool Member Targets:

• LoadBalancerPoolMemberTargetResourceTypeSubnetReservedIPConst

For Profile Targetable Resource Types:

• LoadBalancerProfileTargetableResourceTypesTypeEnumConst
• Values: instance, subnet_reserved_ip, load_balancer, ip

Documentation Updates

• Updated comments for LoadBalancerPoolMemberTarget* models
• Expanded load balancer profile documentation to include targetable_resource_types
• Clarified reserved IP semantics vs plain IP semantics

v0.72.1

Compare Source

Bug Fixes

• Network ACL & Security Group Rules: Fixed discriminator issue on v0.72.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.72.0...v0.72.1

v0.72.0

Compare Source

What's Changed

Version Update

• API Version: 2025-09-16 to 2025-09-17

Major Changes

File Share (NFS) Enhancements (Share struct)

New Properties Added:

• allowed_access_protocols: Specifies allowed access protocols (currently only nfs4)
• availability_mode: Added regional/zonal data availability modes (regional, zonal)
• bandwidth: Maximum bandwidth in megabits per second
• storage_generation: Storage generation identifier (1 or 2)

Enhanced Properties:

• allowed_transit_encryption_modes: Expanded from none/user_managed to none/ipsec/stunnel
• iops: Updated documentation to remove per-client restrictions
• zone: Now optional for shares with availability_mode of regional

Share Profile Enhancements (ShareProfile struct)

• Added comprehensive profile properties:
  • allowed_access_protocols (ShareProfileAllowedAccessProtocols)
  • allowed_transit_encryption_modes (ShareProfileAllowedTransitEncryptionModes)
  • availability_modes (ShareProfileAvailabilityModes)
  • bandwidth (ShareProfileBandwidth)
  • storage_generation (ShareProfileStorageGeneration)

Share Mount Target Changes (ShareMountTarget struct)

• New Required Property: access_protocol (currently only nfs4)
• Enhanced Transit Encryption: Updated from none/user_managed to none/ipsec/stunnel
• Protocol Validation: Mount target access protocol must be listed in share's allowed_access_protocols

Share Mount Target Prototype Changes (ShareMountTargetPrototype, ShareMountTargetPrototypeShareMountTargetByAccessControlModeSecurityGroup, ShareMountTargetPrototypeShareMountTargetByAccessControlModeVPC)

• Added required access_protocol field
• Changed transit_encryption from optional to required
• Updated transit encryption values

Share Snapshot Changes (ShareSnapshot struct)

• Zone Property: Now optional for snapshots of shares with availability_mode of regional

Share Patch Changes (SharePatch struct)

• Added allowed_access_protocols field
• Added bandwidth field
• Updated allowed_transit_encryption_modes values

Share Prototype Changes (SharePrototype, SharePrototypeShareBySize, SharePrototypeShareBySourceShare, SharePrototypeShareBySourceSnapshot, SharePrototypeShareByOriginShare)

• Added allowed_access_protocols field
• Added bandwidth field
• Updated allowed_transit_encryption_modes values and documentation
• Made zone optional for regional availability mode
• Added storage generation compatibility requirements

Share Prototype Share Context Changes (SharePrototypeShareContext)

• Updated transit encryption documentation
• Made zone optional

New Profile Model Structures

• ShareProfileAllowedAccessProtocols and ShareProfileAllowedAccessProtocolsSubset
• ShareProfileAllowedTransitEncryptionModes and ShareProfileAllowedTransitEncryptionModesSubset
• ShareProfileAvailabilityModes, ShareProfileAvailabilityModesEnum, ShareProfileAvailabilityModesFixed
• ShareProfileBandwidth, ShareProfileBandwidthRange, ShareProfileBandwidthDependent, ShareProfileBandwidthFixed, ShareProfileBandwidthEnum, ShareProfileBandwidthDependentRange
• ShareProfileStorageGeneration and ShareProfileStorageGenerationFixed

Breaking Changes

1. Share Mount Target Prototype (ShareMountTargetPrototype, ShareMountTargetPrototypeShareMountTargetByAccessControlModeSecurityGroup, ShareMountTargetPrototypeShareMountTargetByAccessControlModeVPC) now requires:

   • access_protocol (required field)
   • transit_encryption (changed from optional to required)

2. Transit Encryption Mode Values changed across multiple structs:

   • user_managed → ipsec
   • Added stunnel option

3. Constructor Changes:

   • ShareMountTargetPrototype constructors now require access_protocol and transit_encryption parameters
   • Various share constructors (SharePrototypeShareBySize, SharePrototypeShareBySourceShare) no longer require zone parameter when using regional availability

New Constants Added

For Share Mount Target:

• ShareMountTargetAccessProtocolNfs4Const
• ShareMountTargetTransitEncryptionIpsecConst, ShareMountTargetTransitEncryptionStunnelConst

For Share:

• ShareAllowedAccessProtocolsNfs4Const
• ShareAvailabilityModeRegionalConst, ShareAvailabilityModeZonalConst
• ShareAllowedTransitEncryptionModesIpsecConst, ShareAllowedTransitEncryptionModesStunnelConst

For Share Profile:

• Multiple new constants for bandwidth types, availability modes, and access protocols

Documentation Updates

• Enhanced comments throughout all affected structs

v0.71.2

Compare Source

Bug Fixes

• Network ACL & Security Group Rules: Fixed discriminator issue on v0.71.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.71.1...v0.71.2

v0.71.1

Compare Source

What's Changed

• feat(spec): updated the sdk as per the api spec released on 2025-09-01

v0.71.0

Compare Source

What's Changed

• feat(spec): updated the sdk as per the api spec released on 2025-09-01

Full Changelog: IBM/vpc-go-sdk@v0.70.1...v0.71.0

v0.70.2

Compare Source

Bug Fixes

• Network ACL & Security Group Rules: Fixed discriminator issue on v0.70.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.70.1...v0.70.2

v0.70.1

Compare Source

Highlights

• Introduced Allowed Use Constraints for images, volumes, snapshots, and bare metal server disks
• Added new APIs to list compatible instance and server profiles
• Extended models with allowed_use struct definitions
• Improved validations and structured error propagation for new APIs
• fix(template): correctly unmarshal InstanceTemplate response by type

---

Allowed use compatibility constraints (Feature)

• Added support for compatibility filtering using allowed_use expressions, enabling fine-grained control over provisioning:

  • Applies to Image, Snapshot, Volume, and BareMetalServerDisk

  • Evaluates provisioning constraints like:

    • enable_secure_boot, gpu.count, gpu.memory, gpu.model, gpu.manufacturer

• Added new types:

  • ImageAllowedUse, SnapshotAllowedUse, ImageAllowedUsePrototype, ImageAllowedUsePatch
  • BareMetalServerDiskAllowedUse, SnapshotAllowedUsePrototype, SnapshotAllowedUsePatch

• Expressions are validated during create, patch, and provisioning workflows

---

Profile compatibility listing APIs

• Added APIs to list compatible instance or server profiles based on allowed_use expressions:

  • ListImageInstanceProfiles
  • ListImageBareMetalServerProfiles
  • ListSnapshotInstanceProfiles
  • ListVolumeInstanceProfiles

• Each API supports:

  • Pagination (start, limit)
  • Context propagation (WithContext variants)
  • Query parameter-based versioning and generation enforcement

---

Struct and field extensions

• Extended existing models with new allowed_use fields:

  • Image, Snapshot, ImagePatch, ImagePrototype, BareMetalServerDisk

• Added corresponding unmarshalling and validation logic for all additions

• Patch methods now include allowed_use patch helpers and AsPatch() extensions

---

Documentation & code comments

• Enhanced documentation for:

  • CreateInstance, UpdateInstance, CreateBareMetalServer, UpdateBareMetalServer, and similar methods
  • CreateEndpointGateway now documents prototype structure and validation logic
  • ListEndpointGateways explicitly defines sort behavior

---

Breaking Changes

• No methods or types were removed

v0.70.0

Compare Source

Highlights

• Introduced Allowed Use Constraints for images, volumes, snapshots, and bare metal server disks
• Added new APIs to list compatible instance and server profiles
• Extended models with allowed_use struct definitions
• Improved validations and structured error propagation for new APIs

---

Allowed use compatibility constraints (Feature)

• Added support for compatibility filtering using allowed_use expressions, enabling fine-grained control over provisioning:

  • Applies to Image, Snapshot, Volume, and BareMetalServerDisk

  • Evaluates provisioning constraints like:

    • enable_secure_boot, gpu.count, gpu.memory, gpu.model, gpu.manufacturer

• Added new types:

  • ImageAllowedUse, SnapshotAllowedUse, ImageAllowedUsePrototype, ImageAllowedUsePatch
  • BareMetalServerDiskAllowedUse, SnapshotAllowedUsePrototype, SnapshotAllowedUsePatch

• Expressions are validated during create, patch, and provisioning workflows

---

Profile compatibility listing APIs

• Added APIs to list compatible instance or server profiles based on allowed_use expressions:

  • ListImageInstanceProfiles
  • ListImageBareMetalServerProfiles
  • ListSnapshotInstanceProfiles
  • ListVolumeInstanceProfiles

• Each API supports:

  • Pagination (start, limit)
  • Context propagation (WithContext variants)
  • Query parameter-based versioning and generation enforcement

---

Struct and field extensions

• Extended existing models with new allowed_use fields:

  • Image, Snapshot, ImagePatch, ImagePrototype, BareMetalServerDisk

• Added corresponding unmarshalling and validation logic for all additions

• Patch methods now include allowed_use patch helpers and AsPatch() extensions

---

Documentation & code comments

• Enhanced documentation for:

  • CreateInstance, UpdateInstance, CreateBareMetalServer, UpdateBareMetalServer, and similar methods
  • CreateEndpointGateway now documents prototype structure and validation logic
  • ListEndpointGateways explicitly defines sort behavior

---

Breaking Changes

• No methods or types were removed

v0.69.2

Compare Source

Bug Fixes

• Network ACL & Security Group Rules: Fixed discriminator issue on v0.69.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.69.1...v0.69.2

---

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]

ℹ️ 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.24.0
github.com/IBM/go-sdk-core/v5	v5.20.1 -> v5.21.2
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.38.0
golang.org/x/text	v0.23.0 -> v0.31.0
sigs.k8s.io/yaml	v1.4.0 -> v1.6.0