Releases: cloudposse-terraform-components/aws-lambda
v1.536.1
🤖 Automatic Updates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#26)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#25)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
chore(deps): update terraform cloudposse/iam-policy/aws to v2 @[renovate[bot]](https://github.com/apps/renovate) (#6)
This PR contains the following updates:| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/iam-policy/aws (source) | module | major | 1.0.1 -> 2.0.2 |
Release Notes
cloudposse/terraform-aws-iam-policy (cloudposse/iam-policy/aws)
v2.0.2
feat: support policy attachments @nitrocode (#52)
what
- feat: support policy attachments
why
- It's very convenient to be able to attach managed policies or attach inline policies to roles in a single module
- All cloudposse modules that use IAM roles and policies have to reinvent this technology and support both inline and managed. For a while, cloudposse defaulted to creating managed policies which isnt best practice. Each module is getting updated to support inline as an option. To make this easier, this module can support a toggle and then this module can be adopted into the other modules to make it easier to support both cases.
references
- closes #21
Update Readme @Benbentwo (#46)
what
- Small appearance tweaks to readme
why
- cleanup from interpolation by GitHub
🤖 Automatic Updates
Migrate new test account @osterman (#51)
what
- Update
.github/settings.yml - Update
.github/chatops.ymlfiles
why
- Re-apply
.github/settings.ymlfrom org level to getterratestenvironment - Migrate to new
testaccount
References
- DEV-388 Automate clean up of test account in new organization
- DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
- DEV-386 Update terratest to use new testing account with GitHub OIDC
Update .github/settings.yml @osterman (#50)
what
- Update
.github/settings.yml - Drop
.github/auto-release.ymlfiles
why
- Re-apply
.github/settings.ymlfrom org level - Use organization level auto-release settings
references
- DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update release workflow to allow pull-requests: write @osterman (#48)
what
- Update workflow (
.github/workflows/release.yaml) to have permission to comment on PR
why
- So we can support commenting on PRs with a link to the release
Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#47)
what
- Update workflows (
.github/workflows) to use shared workflows from.githubrepo
why
- Reduce nested levels of reusable workflows
Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#45)
what
- Update workflows (
.github/workflows) to addissue: writepermission needed by ReviewDogtflintaction
why
- The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @osterman (#44)
what
- Update workflows (
.github/workflows/settings.yaml)
why
- Support new readme generation workflow.
- Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#41)
what
- Install latest GitHub Action Workflows
why
- Use shared workflows from
cldouposse/.githubrepository - Simplify management of workflows from centralized hub of configuration
Add GitHub Settings @osterman (#36)
what
- Install a repository config (
.github/settings.yaml)
why
- Programmatically manage GitHub repo settings
Update README.md and docs @cloudpossebot (#33)
what
This is an auto-generated PR that updates the README.md and docs
why
To have most recent changes of README.md and doc from origin templates
Update Scaffolding @osterman (#34)
what
- Reran
make readmeto rebuildREADME.mdfromREADME.yaml - Migrate to square badges
- Add scaffolding for repo settings and Mergify
why
- Upstream template changed in the
.githubrepo - Work better with repository rulesets
- Modernize look & feel
Update README.md and docs @cloudpossebot (#32)
what
This is an auto-generated PR that updates the README.md and docs
why
To have most recent changes of README.md and doc from origin templates
v2.0.1
🐛 Bug Fixes
Remove problematic conditional @Nuru (#31)
what
- Remove problematic conditional
why
local.deprecated_statements_valuescan be a tuple, and Terraform does not have a concept of an empty or null tuple to use as an alternative in a conditional, so you can get an error like:
The true and false result expressions must have consistent types. The 'true' tuple has length 0, but the 'false' tuple has length 2.
references
v2.0.0: Revert breaking change in 1.0, add new breaking change
Revert deprecated input to type "any" @Nuru (#30)
Breaking Change
The iam_policy input introduced in v1.0.0 has been changed from type object to type list(object). This allows multiple policy objects to be provided, but more importantly, allows no input or allows the iam_policy input to be used along with the deprecated iam_policy_statements input.
Reversion of Breaking Change
In v1.0.0, the iam_policy_statements input was deprecated, but it was also converted from type any to type map(object), which was how it was documented. However, it was, in practice, allowed to be a list or a map, and many users were supplying lists. This made it an unintentional breaking change for those users.
In this release, iam_policy_statements (while still deprecated) is reverted to type any and accepts both a map and a list.
what
- Revert
iam_policy_statementsback totype = any - Convert
iam_policyinput tolist - Update documentation
why
- Preserve backward compatibility with pre v1.0 module
- Enable all inputs to be used in any combination
- Reflect changes to usage, remove leftovers from initial template
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
chore(deps): update terraform cloudposse/stack-config/yaml to v1.8.0 @[renovate[bot]](https://github.com/apps/...
Contributors
Assets 2
v1.536.0
fix: 'Missing required argument' when using image_uri @supersidor (#16)
## whatWhile applying Lambda component from image_uri next error reported: "s3_key": all of s3_bucket,s3_key must be specified
The reason for this problem is that locals.s3_key is always not null, which conflicts with not null image_url
(see cloudposse/lambda-function/aws).
The solution is to add a additional check when generating locals.s3_key
how to reproduce
components:
terraform:
lambda2-test/lambda:
metadata:
component: lambda
vars:
name: my-service-lambda-test
service_name: lambda2-test
package_type: Image
timeout: 15
image_uri: "778631511111.dkr.ecr.us-east-1.amazonaws.com/hello:latest"
image_config:
command:
- "test.handler.handler"why
Lambda component should work with image_url variable
references
Summary by CodeRabbit
- Chores
- Updated internal asset handling to better manage image inputs, ensuring more streamlined processing in the background.
