Active active regions datasource #605
Merged
Conversation
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
burythehammer
changed the title
burythehammer
force-pushed
the
feat/active-active-regions-datasource
branch
from
02cd72e to
f6e8b1e
Compare
burythehammer
force-pushed
the
feat/active-active-regions-datasource
branch
from
6911c66 to
abb22c5
Compare
burythehammer
force-pushed
the
feat/active-active-regions-datasource
branch
from
4669ae9 to
7fe34e1
Compare
burythehammer
added a commit
that referenced
this pull request
Nov 10, 2025
…asource Active active regions datasource
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Active active regions datasource. Integrates the latest version of the API to feed back all sources.
The raw API call to the staging API does not return the full information back - I've tried this with empty interfaces and the raw response does not contain the necessary information. Therefore the tests are failing.
API tests operate correctly for the other project, confirming there is no marshalling/unmarshalling issue, and when I run terraform (the same terraform from the acceptance tests) and a manual swagger API call then the API returns properly with all the information - so I don't understand what is specifically wrong about the acceptance tests.