Configure profile for efiler-api (or whatever you want to call it) following these instructions here and the following command aws configure sso --profile efiler-api and following the rest of the instructions. Choose the "E-Filer API - Non-Prod" account.
Create .env file in the root with the following AWS_PROFILE=efiler-api (or whatever you named the profile), as well as setting GYR_EFILER_RELEASES_AWS_ACCESS_KEY_ID and GYR_EFILER_RELEASES_AWS_SECRET_ACCESS_KEY to the vita-min development AWS access key (found in rails development credentials).
To install the Java GYR e-filer code, run the following command: bundle exec ruby scripts/download_gyr_efiler.rb
Download Postman to make API requests. This is the tax specific postman URL.
Download the test client private keys from Lastpass. There are two in a note called "EFiler API testing files".
In the variables tab of the Efiler API collection in Postman, set the api_client_private_key to the contents of one of the private keys you downloaded using cat <private_key_file> | pbcopy. Ensure that you ONLY change the "Current version" of the variable, as the "Initial version" will be synced up to Postman's servers and we're trying to avoid that.
Then, change the "Current value" of the api_client_name variable to the base name of the file you chose (e.g. efiler_api_test_client without the .key) and save the collection with Cmd-S.
Additionally, to send /submit requests from Postman, you must provide a submission_bundle with the request. You can download one from the same "EFiler API testing files" note in Lastpass. In the Body tab of the Submit request, remove any contents from the submission_bundle's Value field and replace it with the file you downloaded by clicking the field then selecting "+ New file from local machine".
To run the linter locally, run the following command: bundle exec standardrb --fix. If you forget to do this, the linter will run when a branch pushed up. To ignore the linter, here is a guide.