-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run API test in GitHub Actions #576
Comments
A project plan for this issue is underway. We need to restructure the project to lazy-load our Using this approach the In the future we will need to mock the boto client, which can be done using the moto client, but for now it is sufficient to throw an I'll include a draft project plan down below. My plan is to update the PP as my general solution and implementation progresses. |
Deleted PP from this issue, since it was more relevant to issue #530 |
@Joshua-Douglas good write up. @ju1es has created separate issues to implement a config system. The implementation of this proposed configuration design can close #530 too. Create Config System #522 - This is where it started and is closed now |
We'll have a specific staging environment that's distinct from what we have/will have at In the write-up #576 (comment), I called it "deployed test dev" for lack of a better word or description. I included some information about the |
Thanks for adding that section @paulespinosa! Design is still in draft form, but I should be done (with an implementation for the most important parts) by Monday. I'm hoping to close #522 & #530 with this issue since these are closely related. It should partially address #529, but not fully since I won't touch the front end app in this issue. |
Hey @paulespinosa - I thought about your comments a bit more and decided that it would be much clearer if we moved the research to #530. Thanks for the heads up on that issue. |
Moved to ice box since this issue depends on #530. |
@Joshua-Douglas Sounds good! Thank you. |
Overview
The API tests fail when run in a GitHub Action.
Action Items
Resources/Instructions
GitHub workflows do not have AWS credentials or any other environment variables found in the
.env
file. Try running the tests without a.env
on your local machine to check for test failures.An example of the test failures is shown in Create build-deploy-ec2.yml
The text was updated successfully, but these errors were encountered: