Can no longer deploy Cloudformation where API Gateway is in a different file than the Lambda

[saratitan]

We had to separate our API Gateway put it in one file (api.yaml) and have our lambdas in another (serverless.yaml), and then have the API being a imported value in serverless.yaml

  BaseRequest:
    Type: AWS::Serverless::Function
    Properties:
      ...
      Events:
        GetResource:
          Type: Api
          Properties:
            RestApiId:
              Fn::ImportValue:
                !Sub ${Service}-apigateway-${Environment}
            Path: /{countryId}/{path}
            Method: GET
        PostResource:
          Type: Api
          Properties:
            RestApiId:
              Fn::ImportValue:
                !Sub ${Service}-apigateway-${Environment}
            Path: /{countryId}/{path}
            Method: POST

This was never an issue up until a week ago, where we now receive the following error:

Failed to create the changeset: Waiter ChangeSetCreateComplete failed: Waiter encountered a terminal failure state Status: FAILED. Reason: Transform AWS::Serverless-2016-10-31 failed with: Invalid Serverless Application Specification document. Number of errors found: 1. Resource with id [BaseRequest] is invalid. Event with id [PostResource] is invalid. RestApiId must be a valid reference to an 'AWS::Serverless::Api' resource in same templatemake

One option would be to move the depending Lambda to api.yaml but we would like to have all of our Lambdas together in one file.

[ashwgupt]

Is this error fixed for you?

What wonders me the most is that, how did you ever made it working as we couldn't ever extract our API Gateway out from the SAM Template file as the SAM would fail with error "The RestApiId must be a valid reference of serverless:api type resource in the same template file".

Would you mind sharing your Api gateway SAM file (or did you use plain CF and not SAM) that you used to create the Api Gateway?

[saratitan]

We tried to redeploy today and we received the same error as before, so the issue has not been resolved.

This is our api.yaml:

  ApiGateway:
    Type: AWS::Serverless::Api
    Properties:
      StageName: !Ref Environment
      DefinitionBody:
        Fn::Transform:
          Name: AWS::Include
          Parameters:
            Location: !Ref Swagger

Outputs:
  ApiGatewayRef:
    Description: ...
    Value: !Ref ApiGateway
    Export:
      Name: !Sub ${Service}-apigateway-${Environment}

The exported value is then referenced in the lambda resource as seen in the original post.

We had this on two projects and both stopped working. One of the projects was in production so it caused us a bit of a problem.

[jadamsdb]

Any updates on what you did to resolve this (if you did)? Running into the same issues.

[brettstack]

We currently only support !Ref for RestApiId. We'll update documentation to reflect this.