failed to find a stack error

[0xNarumi]

Support Question

Question

I can't figure out what is causing failed to find a stack error

Plus, when I successfully deployed with rest apiType option,
I got {"message":"Missing Authentication Token"} response

Command Run
sls create_domain and sls deploy

Console Output

Error: Failed to find a stack <project name>

    at CloudFormationWrapper.<anonymous>

Domain Manager Configuration
Replace this with your own serverless.yml file (anonymized, of course) to help us better resolve your issue.

 customDomain:
    basePath: ''
    domainName: ${self:custom.domains.${self:provider.stage}}
    securityPolicy: tls_1_2
    certificateName: '*.domain.im'
    stage: ${self:provider.stage}
    createRoute53Record: true
    endpointType: REGIONAL
    apiType: http

 customDomain:
    basePath: ''
    domainName: ${self:custom.domains.${self:provider.stage}}
    securityPolicy: tls_1_2
    certificateName: '*.domain.im'
    stage: ${self:provider.stage}
    createRoute53Record: true
    endpointType: REGIONAL
    apiType: rest

first yml config didn't work but the second did.
why can't apiType http find a stack?

FYI, this is my lambda function config.

functions:
  api:
    handler: src/index.handler
    events:
      - http:
          path: '{proxy+}'
          method: any
    timeout: 30

Versions

• Domain Manager version(s): 7.3.3
• Serverless Version: Framework Core: 3.38.0
• Lambda Code : Javascript

[0xNarumi]

 customDomain:
    basePath: ''
    domainName: ${self:custom.domains.${self:provider.stage}}
    securityPolicy: tls_1_2
    certificateName: '*.domain.im'
    stage: ${self:provider.stage}
    createRoute53Record: true
    endpointType: REGIONAL
    apiType: http

In my opinion, it seems that when the API gateway is created, an API type with "http" is not being generated. Even though I have configured the YAML as shown above, upon checking after a failure, there always seems to be a gateway created with "rest" as the API type.

[rddimon]

Hi @0xNarumi

It should be fixed in the version v7.3.5

Please try it out and let us know the result