Comments (11)
Hey guys,
Any updates on this? This is the one module blocking us from upgrading to >v4 AWS provider
from terraform-aws-cloudfront-s3-cdn.
The latest AWS 4.release does not contain the breaking changes to S3. Could we have an update to this module that works with AWS 4.19, please?
from terraform-aws-cloudfront-s3-cdn.
I've got a fairly untested migration to aws provider > 4.0.0 in a branch on a fork over here https://github.com/EIGTech/terraform-aws-cloudfront-s3-cdn/tree/4.0.0-aws-provider
I am no terraform expert, and the update definitely shows. A couple of changes required decisions to be made that broke the public API of the module, and I am fairly certain that things could be cleaned up quite a bit. If anyone wants to use this to take a swing at a PR that would be accepted, feel free.
from terraform-aws-cloudfront-s3-cdn.
Yes, came here to say this. I am getting version errors when using this module with the s3 module https://github.com/cloudposse/terraform-aws-s3-bucket v2.0.3
│ Error: Failed to query available provider packages │ │ Could not retrieve the list of available versions for provider │ hashicorp/aws: no available releases match the given constraints >= 2.0.0, │ >= 3.0.0, >= 3.64.0, < 4.0.0, >= 4.9.0
from terraform-aws-cloudfront-s3-cdn.
I'm having the same issue
from terraform-aws-cloudfront-s3-cdn.
We are having the same issue when trying to upgrade
from terraform-aws-cloudfront-s3-cdn.
Version 0.82.3 adds a provider restriction and the module work ok (https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/releases/tag/0.82.3).
from terraform-aws-cloudfront-s3-cdn.
Yes, the breaking changes in AWS provider v4.0.0 did, in fact, break this module and many others. You should pin your providers in your top-level components, using either version blocks (usually in versions.tf
) or via .terraform.lock.hcl
files.
This module will be updated to support v4 eventually, but most likely will have its own breaking changes and will surely require manual migration steps when it is released. See, for an example of our thinking about how to upgrades modules like this one, how we upgraded terraform-aws-s3-bucket and terraform-aws-s3-log-storage.
from terraform-aws-cloudfront-s3-cdn.
I am on the same boat, upgrading to 0.82.x of this module puts a < 4.0.0 restriction on the AWS provider which is breaking my s3 configuration, because aws_s3_bucket_object was replaced by aws_s3_object.
from terraform-aws-cloudfront-s3-cdn.
same here
Yes, came here to say this. I am getting version errors when using this module with the s3 module https://github.com/cloudposse/terraform-aws-s3-bucket v2.0.3
│ Error: Failed to query available provider packages │ │ Could not retrieve the list of available versions for provider │ hashicorp/aws: no available releases match the given constraints >= 2.0.0, │ >= 3.0.0, >= 3.64.0, < 4.0.0, >= 4.9.0
from terraform-aws-cloudfront-s3-cdn.
Same issue, can't use it with the most recent S3 module
from terraform-aws-cloudfront-s3-cdn.
Related Issues (20)
- Error: An argument named "response_headers_policy_id" is not expected here. HOT 5
- Make random_password.referer available as an output HOT 1
- AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-west-2'
- IAM Continuously Updates Between Apply HOT 1
- Using existing origin access identity fails with explicit context HOT 1
- Lambda@Edge submodule doesn't allow to control log group settings HOT 1
- Add support for origin-access-control to replace origin-access-identity HOT 2
- Allow route53 records overwrite
- `additional_bucket_policy` has no effect HOT 1
- The parameter ForwardedValues is required error if i use ordered_cache parameter HOT 2
- Cannot create deployment principal and the CDN in the same terraform run HOT 1
- http2and3 http_version gives validation error
- Ability to attach a custom iAM policy to lambdas
- There are many deprecated resources related to S3 HOT 1
- Unable to disable logging
- Changes To S3 Bucket Default Settings Breaks Access Logging HOT 3
- Unable to reference an origin bucket that does not existing yet
- Website enabled forces an S3 bucket SSL only access policy that can not be applied
- Version 5.0.0 of the aws provider contains breaking changes for this module HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-aws-cloudfront-s3-cdn.