Skip to content

Advnet multi tunnel - #310

Merged
sorinslavic merged 2 commits into
AdobeDocs:mainfrom
sorinslavic:advnet-multi-tunnel
Sep 8, 2026
Merged

sorinslavic merged 2 commits into
AdobeDocs:mainfrom
sorinslavic:advnet-multi-tunnel

Conversation

@sorinslavic

Copy link
Copy Markdown
Contributor

reopen pr#308

Description

Mirrors the BGP dynamic routing additions across both published specs (static/api.yaml and static/models.yaml) for the VPN network infrastructure schemas:

  • VpnConnection — added bgpAsn, bgpPeeringAddress, adobeApipaAddress
  • NetworkInfrastructure — added adobeAsn; documented multi-connection support (recommended max 20) and static/BGP mix in the connections description
  • GatewayInfrastructure — addressSpace is no longer required (it's optional when a connection uses BGP dynamic routing; required only for static-routing connections)

Related Issue

N/A — documentation update tracking the network-infrastructure BGP feature.

Motivation and Context

The self-service-gateway now supports BGP dynamic routing for VPN network infrastructures. The public API reference did not describe the new fields (bgpAsn, bgpPeeringAddress, adobeApipaAddress, adobeAsn) or the relaxed addressSpace requirement, so integrators had no documented way to configure dynamic routing. This change brings the two published specs in line with the implementation. Field descriptions and constraints were verified against the cm-hub self-service-gateway source of truth (VpnInfrastructureRepresentation, NetworkInfrastructureService).

How Has This Been Tested?

  • Both static/api.yaml and static/models.yaml parse cleanly as YAML.
  • Each documented constraint cross-checked against cm-hub validation code (APIPA range 169.254.21.0–169.254.22.255, adobeAsn range 64512–65514/65521–65534, bgpAsn↔bgpPeeringAddress co-presence, MAX_VPN_CONNECTIONS = 20, conditional addressSpace requirement).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Generated with assistance from Claude Code (claude.ai/code)

@sorinslavic
sorinslavic merged commit 18d7532 into AdobeDocs:main Sep 8, 2026
2 checks passed
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.

1 participant