Skip to content

adding auditevent examples and text#1663

Open
bwang-icf wants to merge 3 commits into
masterfrom
brandon/BB2-4968-swagger-auditevent
Open

adding auditevent examples and text#1663
bwang-icf wants to merge 3 commits into
masterfrom
brandon/BB2-4968-swagger-auditevent

Conversation

@bwang-icf

Copy link
Copy Markdown
Contributor

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:

  • Adds any new software dependencies
  • Modifies any security controls
  • Adds new transmission or storage of data
  • Any other changes that could possibly affect security?
  • Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
    security engineer's approval.

Any Migrations?

  • Yes, there are migrations
    • The migrations should be run PRIOR to the code being deployed
    • The migrations should be run AFTER the code is deployed
    • There is a more complicated migration plan (downtime,
      etc)
  • No migrations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant