adding auditevent examples and text#1663
Open
bwang-icf wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
JIRA Ticket:
BB2-4968
What Does This PR Do?
Adds AuditEvent to the swagger documents
What Should Reviewers Watch For?
Anything else missing or any notable differences between the responses given and what is retrievable from the endpoint.
Validation
You will need to obtain a CAN token and then make a GET request to /v3/fhir/AuditEvent as well as /v3/fhir/AuditEvent with a resource id provided. If you're testing this locally, you can disable the client_credentials_validation flag and ensure that the auditevents flag is turned on. Once the auditevents flag is on, you may need to rerun make run-local to ensure the protected capabilities are spun up as well. You will also need to run make collectstatic to see the changes.
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following:
security engineer's approval.
Any Migrations?
etc)