Comments (7)
Just dug around a bunch of external dependencies and noticed that this is what is causing something have contraints mismatch when attempting to use the lacework provider pinned at a certain version.
For instance we are pinning to version ~> 0.2, ~>0.25 (which don't conflict but work out to be 0.27.0) because we are not ready to jump to some of the other higher dependencies, aws provider being one of them.
module "lacework_config" {
source = "lacework/config/aws"
version = "0.7"
}
module "lacework_cloudtrail" {
source = "lacework/cloudtrail/aws"
version = "1.0.2"
}
However, since late last week there was an update to the lacework/iam-role/aws
(which is sourced within the cloudtrail lacework/cloudtrail/aws
module that is versioned as 0.4.1 which is within the current ~> 0.1 that our older 1.0.2 version cloudtrail module sources which creates a dependency on ~> 1.0, ~> 1.15 provider which is conflicting with the current attempt to pin at ~> 0.2 (0.27.0) and outputting an error when doing a terragrunt init due to the collision of version requirements.
Could not retrieve the list of available versions for provider lacework/lacework: no available releases match the given constraints 0.27.0, ~> 1.0, ~> 1.15
And because this is an external dependency within the cloudtrail module we cannot change/update this without forking and setting this to be different at the moment.
from terraform-aws-cloudtrail.
@robert-mcclary-1uphealth Thank you so much for such detailed feedback. Also, apologies for the troubles.
We are about to hit the one year mark from the release of v0.27.0 of our provider, this version still uses some APIv1 endpoints that are about to be decommissioned in November 2023 (next month), I highly encourage you to do update to the latest version, or at least jump to v1.0.0.
Having said that, we acknowledge that we have put you in a bad spot here since you have no way to continue using the versions you were using. 😞
I am going to work on releasing two more versions of both modules to unblock you with @MaxymVlasov recommendation. Once again, we apologize for the inconveniences.
from terraform-aws-cloudtrail.
Also, "~> 0.3"
is analogue of ">= 0.3, < 1.0"
If you want use ">= 0.3.0, < 0.4"
, you need specify "~> 0.3.0"
from terraform-aws-cloudtrail.
@MaxymVlasov Thank you so much for your feedback, the team is looking into this issue actively. I will come back to you with some updates soon.
from terraform-aws-cloudtrail.
@robert-mcclary-1uphealth here you have them:
- https://github.com/lacework/terraform-aws-config/releases/tag/v0.7.2
- https://github.com/lacework/terraform-aws-cloudtrail/releases/tag/v1.0.3
-- Please, let me know if these versions unblock you.
from terraform-aws-cloudtrail.
Please, feel free to re-open this issue if this hasn't been solved.
from terraform-aws-cloudtrail.
@afiune well, you still pointing modules from 0.4 to 0.99999999999999.
terraform-aws-cloudtrail/main.tf
Line 616 in 984385b
change ~> 0.4
to ~> 0.4.0
to fix that (and probably other occurrence)
Also, I can't reopen issue, only create a new one
from terraform-aws-cloudtrail.
Related Issues (20)
- feat: Allow to filter SNS messages HOT 1
- feat: bucket_logs_enabled logs never expire
- bug: Integrate Existing Consolidated CloudTrail - terraform rerun deletes manually attached SNS topic HOT 2
- feat: CloudTrail log bucket denies HTTP requests HOT 3
- bug: support AWS provider v5.0
- Support for enable_log_file_validation
- feat: Lacework CloudTrail should send logs to CloudWatch HOT 1
- bug: [Action Required] S3 changes to bucket authorization are coming in October 2023 HOT 4
- Dependency conflicts with terraform-aws-cloudtrail
- How to implement this: .... HOT 1
- Outputs reference variables instead of resources created by this module HOT 2
- Support passing tags to S3 bucket HOT 1
- feat: Support s3 notifiers for syndicating cloudtrail to sns
- feat: Use existing S3 bucket for access logging HOT 1
- feat: add a required_providers version constraint HOT 1
- bug: support aws provider version ~> 4.0
- feat: Creating a trail for an organization HOT 2
- feat: Using a custom KMS CMK HOT 7
- bug: Error when using use_existing_access_log_bucket = true HOT 3
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-cloudtrail.