DXCDT-363: Add connection data source #470
Merged
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.
🔧 Changes
Adding support for connection data sources in this PR. They'll be available by quering based on
connection_id
orname
. However it was necessary to include theenabled_clients
as a read only value on the connection resource as we're reusing the same logic as the resource. Historically we removed it when we added theauth0_connection_client
association to prevent race conditions, but removing it is unnecessary if the value is read only on the resource.To note that the description of nested schemas on the connection data source is missing due to faulty behavior
on the resource to data source transformation. This will be tackled in a follow up PR: #471.📚 References
🔬 Testing
📝 Checklist