Added a separate method, role_exists, which calls the API using a HEAD request and returns a boolean which
allows for a smaller network footprint than requiring the full GET request and also doesn't force the client to have knowledge of the status codes to understand whether the role exists.
This is the method we used in the Ruby API and in the Resource methods in the Python API (#32).
Connected Issue/Story
N/A
Changelog
[x] The CHANGELOG has been updated, or
[ ] This PR does not include user-facing changes and doesn't require a
CHANGELOG update
Test coverage
[x] This PR includes new unit and integration tests to go with the code
changes, or
[ ] The changes in this PR do not require tests
Documentation
[x] Docs (e.g. READMEs) were updated in this PR
[ ] A follow-up issue to update official docs has been filed here: [insert issue ID]()
[ ] This PR does not require updating any documentation
Behavior
[ ] This PR changes product behavior and has been reviewed by a PO, or
[ ] These changes are part of a larger initiative that will be reviewed later, or
[x] No behavior was changed with this PR
Security
[ ] Security architect has reviewed the changes in this PR,
[ ] These changes are part of a larger initiative with a separate security review, or
[x] There are no security aspects to these changes
Implemented Changes
Added a separate method,
role_exists, which calls the API using a HEAD request and returns a boolean which allows for a smaller network footprint than requiring the full GET request and also doesn't force the client to have knowledge of the status codes to understand whether the role exists.This is the method we used in the Ruby API and in the Resource methods in the Python API (#32).
Connected Issue/Story
N/A
Changelog
Test coverage
Documentation
READMEs) were updated in this PRBehavior
Security