Provision resources for a test Flusight hub

[bsweger]

We want to onboard the cdcepi/FluSight-forecast-hub to the cloud. Before officially submitting PRs to the CDC, let's test our end-to-end process on a fork of their repo (to minimize the back and forth if we need to correct any problems).

[pulumi]

🍹 The Update (preview) for bsweger/hubverse-aws/hubverse was successful.

Resource Changes

    Name                                                     Type                                                    Operation
+   bsweger-flusight-forecast                                aws:iam/role:Role                                       create
+   bsweger-flusight-forecast-write-bucket-policy            aws:iam/policy:Policy                                   create
+   bsweger-flusight-forecast-allow                          aws:lambda/permission:Permission                        create
+   bsweger-flusight-forecast-transform-model-output-lambda  aws:iam/rolePolicyAttachment:RolePolicyAttachment       create
+   bsweger-flusight-forecast                                aws:s3/bucket:Bucket                                    create
+   bsweger-flusight-forecast-read-bucket-policy             aws:s3/bucketPolicy:BucketPolicy                        create
+   bsweger-flusight-forecast                                aws:iam/rolePolicyAttachment:RolePolicyAttachment       create
+   bsweger-flusight-forecast-public-access-block            aws:s3/bucketPublicAccessBlock:BucketPublicAccessBlock  create
+   bsweger-flusight-forecast-create-notification            aws:s3/bucketNotification:BucketNotification            create

[github-actions]

🍹 preview on hubverse-aws/bsweger/hubverse-aws/hubverse

Pulumi report

Previewing update (hubverse)

View Live: https://app.pulumi.com/bsweger/hubverse-aws/hubverse/previews/33219e92-8a8d-4ebd-8b79-48f9e006736e

@ Previewing update..........

@ Previewing update.....
pulumi:pulumi:Stack hubverse-aws-hubverse running 
@ Previewing update.....
aws:s3:BucketV2 hubverse-assets  
aws:iam:Role hubverse-transform-model-output-role  
aws:iam:Policy hubverse-cloudwatch-write-policy  
aws:s3:Bucket hubverse-cloud  
aws:s3:BucketPolicy hubverse-assets-read-bucket-policy  
aws:lambda:Function hubverse-transform-model-output  
aws:iam:RolePolicyAttachment hubverse-transform-model-output-cloudwatch-policy  
aws:s3:BucketPublicAccessBlock hubverse-cloud-public-access-block  
aws:s3:BucketPolicy hubverse-cloud-read-bucket-policy  
aws:iam:Role hubverse-cloud  
aws:iam:Policy hubverse-cloud-write-bucket-policy  
+  aws:s3:Bucket bsweger-flusight-forecast create 
aws:lambda:Permission hubverse-cloud-allow  
aws:iam:RolePolicyAttachment hubverse-cloud  
aws:s3:BucketNotification hubverse-cloud-create-notification  
aws:iam:RolePolicyAttachment hubverse-cloud-transform-model-output-lambda  
+  aws:s3:BucketPublicAccessBlock bsweger-flusight-forecast-public-access-block create 
+  aws:s3:BucketPolicy bsweger-flusight-forecast-read-bucket-policy create 
+  aws:iam:Role bsweger-flusight-forecast create 
+  aws:iam:Policy bsweger-flusight-forecast-write-bucket-policy create 
+  aws:lambda:Permission bsweger-flusight-forecast-allow create 
+  aws:iam:RolePolicyAttachment bsweger-flusight-forecast create 
+  aws:iam:RolePolicyAttachment bsweger-flusight-forecast-transform-model-output-lambda create 
+  aws:s3:BucketNotification bsweger-flusight-forecast-create-notification create 
pulumi:pulumi:Stack hubverse-aws-hubverse  
Resources:
+ 9 to create
16 unchanged

[nickreich]

The idea here is that you are adding the forked repo on your account to our list of "hubs in the cloud" just to test it out and see what happens? And then we can delete that forked version later? If I'm understanding correctly, then it seems good to me.

[bsweger]

I actually don't know if this will work for a personal GitHub account (instead of an org). We'll find out!