-
Notifications
You must be signed in to change notification settings - Fork 150
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
Issues with outline scenario and aws provider credentials #173
Comments
|
Could you please have a try with |
Looks like there is a certain scenario (the one I was using) it still fails. I am defining two providers, the first one didn't have an alias or keys defined since it was inheriting creds from shell variables. The second provider had an alias (since its required for providers after the first) and had keys set. In that scenario things are still broken, but if I either add keys to both providers or add alias to both providers it works as expected. Test TF and resulting plan json shown below Works as expected
Works as expected
Does not work as expected: test skipped saying no providers have key/secret defined
|
One of my test case was this while I was debugging the problem. Let me check again. |
Ah yes, found the problem. It looks like I tested everything except if there is an AWS provider (defined in the first place) that doesn't have any alias. Now this is also fixed. Releasing |
Worked like a charm. Thanks for the quick turn around on this. |
Description :
I am testing the hardcoded credentials example shown here:
https://terraform-compliance.com/pages/Examples/aws_credentials.html and terraform compliance is skipping the provider saying "SKIPPING: Skipping the step since provider type does not have access_key property."
To Reproduce
1.
Expected behavior :
I expected to have the rule fail due to hardcoded access_key and secret_key being present which match the given regex
Tested versions :
The text was updated successfully, but these errors were encountered: