Update integrations endpoints to v3 #282
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.
Updates references to
admin/v2/integrations
toadmin/v3/integrations
. Thev3
version of the endpoints adds a small breaking change to the integrations fields.Description
Updates references to
admin/v2/integrations
toadmin/v3/integrations
and adds handling for the newuser_access
field on create/update.Motivation and Context
The
v3
endpoints add a newuser_access
field and changes the behavior ofgroups_allowed
.Previously the
groups_allowed
field by itself determined which users could authenticate with the application as described here. Now a third state has been added which allows no users to authenticate.Because of that, the
user_access
field has been added to express this more cleanly, andgroups_allowed
can only be provided ifuser_access === "PERMITTED_GROUPS"
.How Has This Been Tested?
Local test (sorry for blurry video, had to export as 480p to upload :))
https://github.com/user-attachments/assets/33a82208-c100-4ae2-ae7b-3ea594f2a12e
Test Script
https://gist.github.com/ckeif-duo/ae530de40a61ed9ce53af38b9478faf0
Types of Changes