Skip to content

Conversation

@dauntlessnomad
Copy link
Contributor

fix for dynamodb resource not found error in the example.

fix for dynamodb resource not found error in the example.
@antonbabenko antonbabenko changed the title Update main.tf chore: Fixed code in examples (dynamodb resource not found error) Jan 27, 2022
@antonbabenko antonbabenko changed the title chore: Fixed code in examples (dynamodb resource not found error) chore: Fixed code in examples (dynamodb resource not found error) Jan 27, 2022
@antonbabenko antonbabenko merged commit 668d457 into terraform-aws-modules:master Jan 27, 2022
@lorengordon
Copy link
Contributor

@tomahawk-pilot @antonbabenko This change is not valid... There is no data source named "vpc"... This change is causing the pre-commit failures in the pr I opened here, #737

@lorengordon
Copy link
Contributor

(And yes, I am also plugging my PR to try to get review eyes on it 😁)

@dauntlessnomad
Copy link
Contributor Author

@tomahawk-pilot @antonbabenko This change is not valid... There is no data source named "vpc"... This change is causing the pre-commit failures in the pr I opened here, #737

I ran the tf and it works. But on second look it should be module.vpc

@lorengordon
Copy link
Contributor

I suppose it would be good if changes to the examples also ran all the precommit jobs, to catch these things earlier?

@bryantbiggs
Copy link
Member

all code in the module repos are checked by pre-commit - but this is a logic error. you could have just as easily put "foo" instead, the policy doesn't care what value is there - it just gets evaluated as allow or deny

@lorengordon
Copy link
Contributor

Ok... Please look at the PR I linked. Clearly many more tests were run on that PR, and two of them caught this failure.

@bryantbiggs
Copy link
Member

Hmm, actually this one should have been caught. It's syntactically incorrect

@antonbabenko
Copy link
Member

This PR is included in version 3.11.5 🎉

@bryantbiggs
Copy link
Member

So I see the issue here which has caused a flurry of spurious changes. The DynamoDB endpoint is a gateway endpoint and I guess that is not being found by the data source. We can swap this for one of the interface endpoints like SSM

__ OR __

We change the condition to be "aws:SourceVpc" (remove trailing e so its for the VPC and not the VPC endpoint)

harrythebot pushed a commit to lolocompany/terraform-aws-vpc that referenced this pull request May 11, 2022
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants