Skip to content

Bugfix additional policy documents#276

Merged
ofhouse merged 2 commits intomilliHQ:mainfrom
christophebeling:bugfix/additional-lambda-policy-issue
Apr 7, 2022
Merged

Bugfix additional policy documents#276
ofhouse merged 2 commits intomilliHQ:mainfrom
christophebeling:bugfix/additional-lambda-policy-issue

Conversation

@christophebeling
Copy link
Contributor

Add boolean to determine whether we should create additional lambda policies since checking for a json string will fail when using data.aws_iam_policy_document.

…icies since checking for a json string will fail when using data.aws_iam_policy_document
@christophebeling christophebeling force-pushed the bugfix/additional-lambda-policy-issue branch from ddf2300 to ea1157e Compare January 30, 2022 11:58
Copy link
Member

@ofhouse ofhouse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!
Would name the variable lambda_attach_policy_json instead of create_lambda_policy to align with the already existing variable lambda_attach_to_vpc.

Copy link
Member

@ofhouse ofhouse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for adding the suggestions!

@ofhouse ofhouse added this to the Upcoming Minor milestone Feb 1, 2022
@ofhouse ofhouse merged commit 947a801 into milliHQ:main Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants