[apigatewayv1] Manual HTTP Method Creation Required for Resource Integration Setup #2360
Labels
needs-investigation
Indicates an issue needs some investigation.
service/apigateway
Indicates issues or PRs that are related to apigateway-controller.
Describe the bug
api gateway v1 - https://github.com/aws-controllers-k8s/apigateway-controller
Issue with Creating
Integration
forResource
in AWS API Gateway V1There is a limitation when attempting to create an
Integration
for aResource
. The current process requires the HTTP method to be manually established for theResource
using command line tools or Terraform before anIntegration
can be created. This step cannot be bypassed or automated within the current workflow, causing an additional manual step in the integration process.Impact:
This constraint complicates the process of setting up integrations, as it necessitates manual intervention to define the HTTP method on the
Resource
before proceeding. This manual step can hinder automation efforts, making it more challenging to streamline deployment and integration workflows, particularly in environments that rely heavily on Infrastructure as Code (IaC) and automated pipelines.Steps to reproduce
Apply the following yaml file in the cluster
Expected outcome
Integration
should create the http method by automatically by itself, or the ACK should have another kind that creates the http request.Actual Result
The following error displayed in the
.status.conditions
:"NotFoundException: Invalid Method identifier specified"
Environment
EKS Kubernetes version - 1.31
AWS service targeted - Lambda Functions
The text was updated successfully, but these errors were encountered: