forked from dandi/dandi-infrastructure
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Do not merge] PR for diff of DANDI vs. LINC #15
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
allow HEAD requests from different origins.
This silences the warning about using Node 16.
Add CI for terraform linting/validation
We'll want to remove these in a follow-up PR after applying.
Deploy `dandidav` service to Heroku
Remove import blocks in webdav.tf
Neither of these are needed anymore now that we are deploying by pushing directly to Heroku
Disable Rust buildpack and dyno-metadata feature
Increase quantity of web dynos to 3
Add embargoed tags bucket policy
Revert "Add embargoed tags bucket policy"
Add bucket policy statement for embargoed objects
Using just `heroku-community/cli` results in subsequent Terraform plans wanting to change it to the full URL.
Use full URL for webdav buildpack
Use a trailing dot for AWS ACM validation record
Remove trailing dot for ACM CNAME entry
Revert "Remove trailing dot for ACM CNAME entry"
Give Heroku user `s3:PutObjectTagging` permission
Specify developer email list as env var
Allow PutObjectTagging for both production and staging buckets
Add `s3:PutObjectTagging` permission to sponsored bucket
This should allow terraform cloud to authenticate with AWS via a direct trust relationship instead of relying on a manual token placed in the environment variable of TFC. See https://developer.hashicorp.com/terraform/cloud-docs/workspaces/dynamic-provider-credentials#how-dynamic-credentials-work for documentation on how the dynamic credential system works.
We recently upgraded our Heroku Postgres DB. This involved provisioning a new DB instance, which put our Terraform state out of sync.
Import new heroku postgres addon
This has been applied and can now be removed.
Remove import block
Scope trailing delete policy to `blobs` prefix only
Hi @aaronkanzer, perhaps we want this diff in the other direction from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moves dandi#191 into LINC repo
Cc @kabilar