You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 19, 2022. It is now read-only.
Suggest that we remove the alternatives for associating a policy
Currently we can associate a policy with user/team/org with a string id or object (string, variables) as array elements in the payload
If using a string it results in the association being created with empty policy instance variables anyway.
Suggest we enforce just the object elements in the array for associating policies; an empty variables array is effectively then the same as the string id alternative currently in place.
A major reason to do this is swagger does not like joi.alternatives when generating the docs so it adds a little confusion to that endpoint. This would simplify, however it would be a breaking change.
The text was updated successfully, but these errors were encountered:
Suggest that we remove the alternatives for associating a policy
Currently we can associate a policy with user/team/org with a string id or object (string, variables) as array elements in the payload
If using a string it results in the association being created with empty policy instance variables anyway.
Suggest we enforce just the object elements in the array for associating policies; an empty variables array is effectively then the same as the string id alternative currently in place.
A major reason to do this is swagger does not like joi.alternatives when generating the docs so it adds a little confusion to that endpoint. This would simplify, however it would be a breaking change.
The text was updated successfully, but these errors were encountered: