Asap 215 document audit export

[lkacenja]

We want to create a page for document audit export options. We think this will be handy for stakeholders. We want to support a CSV export and guide folks toward our API. Our API documentation is not visible or up to date.

This PR adds the following:

• A new tab on the site for export related activity
• An S3 integrated CSV exporter
• Refactor of our API to include access control that matches the rest of the site
• Remove API endpoints we don't want to or aren't ready to support
• Controller and view for displaying API documentation /api-docs

• What additional steps are required to test this branch locally?

Requires a docker compose build --no-cache to run the revised bucket setup script.

Also requires a yarn install to add the new Swagger UI package.

• Are there any areas you would like extra review?

Would love some help testing out the API endpoints.

• Are there any rake tasks to run on production?

No

[lkacenja]

This PR introduces a move to storing more items in Rails config. These secret names are now in config/environments/development.

[lkacenja]

I moved the insights (dashboard) endpoint here to documents, because it nests under documents in the URL and views directory. I thought this would make more sense.

[lkacenja]

I thought about actually including the user's authorization header here, but it seems more secure not to.

[4dh]

So far, activity exporting looks good, but having some auth issues when testing the API via curl in terminal-

[4dh]

Also adding this interesting error that we saw when generating AI exception:

[lkacenja]

So far, activity exporting looks good, but having some auth issues when testing the API via curl in terminal-

When you get back, maybe we could have a look at the command you are running. Curl requests work for me with the following process:

1. Base64 encode credentials: echo -n '<email>:<password>' | base64
2. Add the encoded value to the authorization header.

curl -X 'GET' \
'http://localhost:3000/api/sites/1/documents?page=0&items_per_page=100' \
-H 'accept: application/json' \
-H 'authorization: Basic <encoded auth goes here>'

[lkacenja]

Thank you for documenting the LocalStack error. I've encountered this a few times as well. When we see this error, I think the LocalStack Lambda service has crashed. I'm not really sure why this happens. To fix it, restart the docker compose and potentially the docker daemon. Usually, rebuilding the images is not required.

[lkacenja]

Given that the API seems to be working ok for me and that the LocalStack error is not related to this branch, I'd like to go ahead and merge this work.