-
Notifications
You must be signed in to change notification settings - Fork 9.7k
Actions plumbing #43669
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
Actions plumbing #43669
Conversation
Community GuidelinesThis comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀 Voting for Prioritization
Pull Request Authors
|
9b49a4c
to
e99ec05
Compare
78c2efb
to
7db6bf8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
if d.HasV6_0SDKv2Fix { | ||
v.errs = append(v.errs, fmt.Errorf("V60SDKv2Fix not supported for Actions: %s", fmt.Sprintf("%s.%s", v.packageName, v.functionName))) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason we check and error only on this annotation? It seems there could be many which don't apply to actions (SingletonIdentity
, WrappedImport
, etc.).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're absolutely right. The V60SDKv2Fix
annotation was specifically created to address a v6.0 provider bug related to the Resource Identity feature that only affected certain SDK-based resources. Since Actions are a new resource type that wasn't affected by that bug, this check is unnecessary.
Looking at the broader pattern, if we want to validate unsupported annotations for Actions, we should either:
- Validate ALL annotations that don't apply to Actions (not just V60SDKv2Fix), or
- Remove this specific check since it's not needed
I'll remove the V60SDKv2Fix check for Actions since it's not applicable.
FYI, rebase on this one #43669: % make t T=TestAccLambdaInvokeAction_ K=lambda
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
make: Running acceptance tests on branch: 🌿 f-lambda-invoke-action 🌿...
TF_ACC=1 go1.24.6 test ./internal/service/lambda/... -v -count 1 -parallel 20 -run='TestAccLambdaInvokeAction_' -timeout 360m -vet=off
2025/09/17 09:58:40 Creating Terraform AWS Provider (SDKv2-style)...
2025/09/17 09:58:40 Initializing Terraform AWS Provider (SDKv2-style)...
=== RUN TestAccLambdaInvokeAction_basic
=== PAUSE TestAccLambdaInvokeAction_basic
=== RUN TestAccLambdaInvokeAction_withQualifier
=== PAUSE TestAccLambdaInvokeAction_withQualifier
=== RUN TestAccLambdaInvokeAction_invocationTypes
=== PAUSE TestAccLambdaInvokeAction_invocationTypes
=== RUN TestAccLambdaInvokeAction_logTypes
=== PAUSE TestAccLambdaInvokeAction_logTypes
=== RUN TestAccLambdaInvokeAction_clientContext
=== PAUSE TestAccLambdaInvokeAction_clientContext
=== RUN TestAccLambdaInvokeAction_complexPayload
=== PAUSE TestAccLambdaInvokeAction_complexPayload
=== CONT TestAccLambdaInvokeAction_basic
=== CONT TestAccLambdaInvokeAction_logTypes
=== CONT TestAccLambdaInvokeAction_complexPayload
=== CONT TestAccLambdaInvokeAction_invocationTypes
=== CONT TestAccLambdaInvokeAction_withQualifier
=== CONT TestAccLambdaInvokeAction_clientContext
--- PASS: TestAccLambdaInvokeAction_withQualifier (29.12s)
--- PASS: TestAccLambdaInvokeAction_clientContext (34.58s)
--- PASS: TestAccLambdaInvokeAction_logTypes (49.21s)
--- PASS: TestAccLambdaInvokeAction_basic (53.73s)
--- PASS: TestAccLambdaInvokeAction_complexPayload (60.50s)
--- PASS: TestAccLambdaInvokeAction_invocationTypes (63.35s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/lambda 68.836s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
Warning This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v6.14.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Description
This PR provides the plumbing necessary to make Terraform Actions work in the Terraform AWS Provider.
Relations
To do:
terraform
core beta release for testing (includes actions: move schema to single action type and remove linked resources terraform#37602)Relations:
aws_lambda_invoke
#43972aws_cloudfront_create_invalidation
#43955aws_ses_send_email
#44214aws_sns_publish
#44232aws_ec2_stop_instance
#43700References
Output from Acceptance Testing
N/A - Cover by `go test` and dependents