S3 buckets and Circle CI export script

[SarahJaine]

Description of change
Merges

• create s3 buckets Terraform: Create S3 bucket for doc upload adhocteam/Head-Start-TTADP#72
• CircleCI results export script CircleCI results export script adhocteam/Head-Start-TTADP#65

Description of change
for adhocteam#72

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

How to test
for adhocteam#72

• Tested against sandbox.
  • There is a new s3 bucket ttahub-document-upload-sandbox in that space > https://dashboard.fr.cloud.gov/services
  • And there is a new service binding for that bucket > https://dashboard.fr.cloud.gov/applications/2oBn9LBurIXUNpfmtZCQTCHnxUM/08d4c228-67c6-47e1-ac9a-bb030c880160/services
• Tested against dev
  • There is a new s3 bucket ttahub-document-upload-sandbox in that space > https://dashboard.fr.cloud.gov/services
    
  • And there is a new service binding for that bucket > https://dashboard.fr.cloud.gov/applications/2oBn9LBurIXUNpfmtZCQTCHnxUM/299f6a1f-f638-4902-a776-ef32788e7773/services
    

Issue(s)

• closes Create s3 buckets for document upload endpoint #149
• closes Figure out workaround for CircleCI access issues #87

Checklist

• Meets issue criteria
• Code tested
• Meets accessibility standards (WCAG 2.1 Levels A, AA)
• Documentation updated
  • API methods
  • Boundary and Data Flow Diagrams
  • Architectural Decision Records written for major infrastructure decisions with the Nygard template
  • OSCAL templates completed when security controls are implemented or modified

[rahearn]

Looks great!

[rahearn]

└─> terraform apply
data.cloudfoundry_service.s3: Refreshing state...
data.cloudfoundry_space.space: Refreshing state... [id=e1fb8eaa-a857-42f0-a46f-7c08da3dfbaa]
data.cloudfoundry_service.rds: Refreshing state... [id=dcfb1d43-f22c-42d3-962c-7ae04eda24e7]
cloudfoundry_service_instance.database: Refreshing state... [id=2bcbcb23-9f3b-44f1-9b37-5d7554d02c3e]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # cloudfoundry_service_instance.document_upload_bucket will be created
  + resource "cloudfoundry_service_instance" "document_upload_bucket" {
      + id               = (known after apply)
      + name             = "ttahub-document-upload-staging"
      + recursive_delete = false
      + service_plan     = "021bb2a3-7e11-4fc2-b06b-d9f5938cd806"
      + space            = "e1fb8eaa-a857-42f0-a46f-7c08da3dfbaa"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

cloudfoundry_service_instance.document_upload_bucket: Creating...
cloudfoundry_service_instance.document_upload_bucket: Creation complete after 6s [id=d06e38cf-81ee-4568-977c-5c5bd1a15cee]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.