-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
provider/aws: Add import support for API Gateway resources #558
Comments
A few more for the API Gateway import list - would love to see these! =]
|
Pull requests submitted:
|
The above mentioned PRs have been merged and released in version 1.33.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
+1 for "aws_api_gateway_deployment" import |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
Please don't forget the aws_api_gateway_deployment import functionality. |
+1 for "aws_api_gateway_deployment" import |
Re:
Before that is implemented (eagerly waiting), I am hacking the
{
"mode": "managed",
"type": "aws_api_gateway_deployment",
"name": "notification_time",
"provider": "provider[\"registry.terraform.io/hashicorp/aws\"]",
"instances": [
{
"schema_version": 0,
"attributes": {
"created_date": "2018-05-29T17:10:43Z",
"description": "",
"execution_arn": "arn:aws:execute-api:us-west-2:111122223333:******/******",
"id": "******",
"invoke_url": "https://******.execute-api.us-west-2.amazonaws.com/******",
"rest_api_id": "******",
"stage_description": null,
"stage_name": "******",
"triggers": null,
"variables": null
},
"sensitive_attributes": [],
"dependencies": [
"aws_api_gateway_integration.notification_time",
"aws_api_gateway_method.notification_time",
"aws_api_gateway_resource.notification_time",
"data.aws_api_gateway_resource.v1",
"data.aws_api_gateway_rest_api.api_gateway"
]
}
]
}, $ terraform version
Terraform v1.1.4
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v3.75.1 |
These would be very useful. +1 for the feature |
I've got a pull request open for the last ask left in this issue, the ability to import |
This functionality has been released in v4.44.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! |
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. |
This issue was originally opened by @Vinnl as hashicorp/terraform#12250. It was migrated here as part of the provider split. The original body of the issue is below.
(I wasn't sure if I had to create separate issues for all of these - most of them are only useful together with some of the others. If you prefer separate issues, do let me know.)
Terraform Version
At least up to v0.8.7
Affected Resource(s)
The following resources are required to set up a proxy integration with an AWS Lambda function for API Gateway, and do not support importability yet:
Expected Behavior
Running the import command for these resources should update the state.
Actual Behavior
Message
resource <resource> doesn't support import
.The text was updated successfully, but these errors were encountered: