Skip to content
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

Create s3 buckets for document upload endpoint #149

Closed
pamlo412 opened this issue Nov 12, 2020 · 0 comments · Fixed by #167
Closed

Create s3 buckets for document upload endpoint #149

pamlo412 opened this issue Nov 12, 2020 · 0 comments · Fixed by #167
Assignees
Labels
1 Story Point enhancement New feature or request In epic 5 Issue is a child in the indicated parent epic Infra Infrastructure V1.0 MVP Indicates the release version for the issue
Milestone

Comments

@pamlo412
Copy link
Contributor

pamlo412 commented Nov 12, 2020

Update terraform code to create s3 buckets to use for document upload (a field in the activity report)

Acceptance criteria

  • 3 s3 buckets; one for each deployed environment: dev, staging, and prod

Exclusions:

@pamlo412 pamlo412 added enhancement New feature or request In epic 5 Issue is a child in the indicated parent epic V1.0 MVP Indicates the release version for the issue labels Nov 12, 2020
@SarahJaine SarahJaine added the Infra Infrastructure label Nov 12, 2020
@SarahJaine SarahJaine changed the title Create s3 buckets for activity reports' file upload endpoint Create s3 buckets for document upload endpoint Nov 12, 2020
@SarahJaine SarahJaine added the 1 Story Point label Nov 12, 2020
@rahearn rahearn added this to the sprint5 milestone Nov 23, 2020
rahearn pushed a commit that referenced this issue Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 Story Point enhancement New feature or request In epic 5 Issue is a child in the indicated parent epic Infra Infrastructure V1.0 MVP Indicates the release version for the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants