-
Notifications
You must be signed in to change notification settings - Fork 200
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
Error: Failed to query available provider packages #173
Comments
This happens to be caused by this commit in the terraform-aws-vpc module, which adds a version constraint to use the AWS provider >= 3.73.0, while we have a constraint to use 3.71.x. Two actions from my side:
|
Fix on the way, will be released as part of v2.4.2. Thanks a lot for reporting! |
Hi ! Think I have the same problem with the latest version (and with version 2.4.2), both using docker and OS install (MacOS)
What OS are you using? What is your Stratus Red Team version? |
Confirmed that this is broken again. |
Caused by this commit of the terraform-aws-vpc module: terraform-aws-modules/terraform-aws-vpc@44e6eaa#diff-dfd5848fa77a04d0343891fe859286cc210473d10f0e62c7f99f0d5ecf1a9927R7 Doesn't seem particularly relevant to bump all Terraform AWS provider versions to 4.x, so I'll work on #191 instead to make sure the version of terraform-aws-vpc is pinned. |
…vable constraints (closes #173)
…vable constraints (closes #173)
Working ! Tried with Just so you know, I had to force the region env var, looks like profile wasn't enough
|
Thanks for checking, will merge now. |
Will be shortly released as part of v2.5.3 |
What is not working?
When I try to detonate for example
aws.credential-access.ec2-steal-instance-credentials
, I get the following error:I confirmed that I'm authenticated against my AWS account through environment variables and I confirmed I can execute other commands like
aws.defense-evasion.cloudtrail-stop
.What OS are you using?
Mac OS X
What is your Stratus Red Team version?
2.4.1
Full output?
Files in $HOME/.stratus-red-team?
The text was updated successfully, but these errors were encountered: