Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

l2 connection - supported aside service token #3

Merged
merged 1 commit into from
Feb 19, 2022

Conversation

ocobles
Copy link
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
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
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 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.

Add Fabric Service Tokens support for L2 Connections
2 participants