You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
When running make test locally, it fails before running the tests with:
An error occurred (AccessDeniedException) when calling the CreateSecret operation: User: arn:aws:iam::733164497221:user/becca is not authorized to perform: secretsmanager:CreateSecret on resource:
<redacted>
This occurs because I don't have sufficient privileges to use AWS secrets manager on my local user account.
One option for fixing it would be that I could just add permissions. However, secrets do have a cost associated with them, and we should only be automating running tests that use free resources. Also, we wouldn't want all contributors to have to add CreateSecret permissions to their local account in order to successfully run tests.
Can we instead disable these tests locally, but leave them enabled remotely?
The text was updated successfully, but these errors were encountered:
When running
make test
locally, it fails before running the tests with:This occurs because I don't have sufficient privileges to use AWS secrets manager on my local user account.
One option for fixing it would be that I could just add permissions. However, secrets do have a cost associated with them, and we should only be automating running tests that use free resources. Also, we wouldn't want all contributors to have to add CreateSecret permissions to their local account in order to successfully run tests.
Can we instead disable these tests locally, but leave them enabled remotely?
The text was updated successfully, but these errors were encountered: