作者:陈小默gg | 来源:互联网 | 2023-09-01 16:46
Openingthisissueasdiscussedishttps://github.com/terraform-providers/terraform-prov
Opening this issue as discussed is https://github.com/terraform-providers/terraform-provider-aws/issues/3192#issuecomment-371764787 where the provider attempts to perform a lambda alias' rename, which is not even an allowed operation.
Terraform Version
0.11.5
Affected Resource(s)
aws_lambda_alias
Terraform configuration files
Please see https://github.com/terraform-providers/terraform-provider-aws/issues/3192#issue-292762854
Expected Behavior
A new alias should be created - the name of an alias should be treated as an unique identifier.
Actual Behavior
An in line update is attempted, which fails with a 404 from the API:
1 2 3 4
| * lambda.aws_lambda_alias.version: 1 error(s) occurred:
* aws_lambda_alias.version: Error updating Lambda alias: ResourceNotFoundException: Alias not found: arn:aws:lambda:us-east-1:999999999999:function:sample-lambda:MASTER-121
status code: 404, request id: ca3401b9-237d-11e8-8e0e-05a5757ee33f |
Steps to Reproduce
- Create and apply a lambda and tag it with aliases according to the scheme shown at the top.
- Change the lambda_version variable.
- terraform apply
References
https://github.com/terraform-providers/terraform-provider-aws/issues/3192
https://github.com/terraform-providers/terraform-provider-aws/issues/3192#issuecomment-371764787
该提问来源于开源项目:hashicorp/terraform-provider-aws
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!