Skip to content
This repository was archived by the owner on Feb 5, 2026. It is now read-only.

l2 connection - supported aside service token#3

Merged
displague merged 1 commit intoequinix:masterfrom
ocobles:ecx_l2_conn_aside_servicetoken
Feb 19, 2022
Merged

l2 connection - supported aside service token#3
displague merged 1 commit intoequinix:masterfrom
ocobles:ecx_l2_conn_aside_servicetoken

Conversation

@ocobles
Copy link
Copy Markdown
Contributor

@ocobles ocobles commented Feb 15, 2022

Added support to create ecx/v3 l2 connections using a Fabric Service Token .

  • Request field is primaryServiceToken
  • Value is returned in the get connection by uuid in vendorToken
  • Value is exposed in the client as ServiceToken
  • This attribute is not supported in redundant connections API calls (secondary attributes), not even from the portal. To create a redundant connection, it will be required two connection requests, one for each service token

fix #2

@displague
Copy link
Copy Markdown
Member

displague commented Feb 17, 2022

It would build reviewer confidence if these new fields were included in the spec (described at https://developer.equinix.com/catalog/buyerv3#operation/createConnectionUsingPOST and https://developer.equinix.com/catalog/buyerv3#operation/getConnectionByUuidUsingGET).

Copy link
Copy Markdown
Member

@displague displague left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the updated tests and fixtures describing the new response field.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Fabric Service Tokens support for L2 Connections

2 participants