This repository was archived by the owner on Feb 5, 2026. It is now read-only.
include 2nd device in API call even when both are same one#10
Merged
Conversation
Signed-off-by: ocobleseqx <[email protected]>
ctreatma
approved these changes
Jul 20, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes issue reported in terraform provider equinix/terraform-provider-equinix#347
It doesn't create the secondary connection if you are using same device as the primary connection. That used to work, but it seems that a recent change to the billing process (it is now possible to create a single connection to Azure, without an SLA provided by Azure) is causing this to fail. There's no reason/use case from the API perspective not to include the second device id