Skip to content
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

aws_api_gateway_intergration_response : Method response not found #7486

Closed
rjinski opened this issue Jul 5, 2016 · 5 comments
Closed

aws_api_gateway_intergration_response : Method response not found #7486

rjinski opened this issue Jul 5, 2016 · 5 comments

Comments

@rjinski
Copy link

rjinski commented Jul 5, 2016

Terraform Version

Terraform v0.6.16

Affected Resource(s)

  • aws_api_gateway_method
  • aws_api_gateway_integration

Terraform Configuration Files

https://gist.github.com/rjinski/b2324266e16f1b79fca25b3ba24e39ed

Debug Output

Error applying plan:

1 error(s) occurred:

  • aws_api_gateway_integration_response.demo: Error creating API Gateway Integration Response: NotFoundException: No integration defined for method
    status code: 404, request id: 28168313-428b-11e6-ada4-e1f298d71627

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Expected Behavior

All resources created successfully.

Actual Behavior

When running terraform apply for the first time the above error is produced stating the the api gateway method resource could not be found however the resource on AWS has been created. Re-running terraform apply all resources are created.

@OJFord
Copy link
Contributor

OJFord commented Oct 29, 2016

I had the same issue, add:

depends_on [
    "aws_api_gateway_integration.your_integration"
]

It would be nice though if this could be automatically taken care of, e.g. by collecting all resources for a method, and doing the integration response last.

@Ninir
Copy link
Contributor

Ninir commented Dec 15, 2016

Hi @rjinski

Added a warning on this in #8049.
While the documentation is updated, the code can also be improved.

@stack72
Copy link
Contributor

stack72 commented Feb 8, 2017

Can this be closed because of #8049?

@OJFord
Copy link
Contributor

OJFord commented Feb 8, 2017

@stack72 I think ideally the behaviour could be improved, such that the docs-only change in #8049 could be reverted.

cf. #8099 and #6613.

@ghost
Copy link

ghost commented Apr 10, 2020

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants