This repository has been archived by the owner on Aug 19, 2022. It is now read-only.
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.
lots of test updates because of one small validation change...
here we are enforcing the use of an object when associating policies as we would if creating a policy instance. Essentially associating a policy with an udaru entity is a policy instance with no variables set anyway, so here we re-use the same object for associating both
swagger documentation is now free of generic objects and does not default to string under POST/PUTs under each entity type.
This is the issue this is addressing: #522
readme may need to be updated