v5.0.11 --> ERROR: Template error: instance of Fn::GetAtt references undefined resource JetsInfoController

[leandro-maciel-sya]

After changing the configuration to:

config.cfn.build.controllers = 'one_lambda_per_controller'
config.cfn.build.routes = 'one_apigw_method_per_route'

on config/application.rb I'm having the following error on my deployment:

ERROR: Template error: instance of Fn::GetAtt references undefined resource JetsInfoController
The Jets application failed to deploy. Jets creates a few CloudFormation stacks
to deploy your application. The logs above show the CloudFormation parent stack
events. You can go to the CloudFormation console and look for the nested stack
with the error. The specific nested stack usually shows more detailed information
and can be used to resolve the issue.

The error is not beeing presented on the CF Stacks so, I was not be able to figure it out what was happening. Do you know what could be wrong?

It was a clean deploy with a brand new created project. It was working before without those params, then I've deleted evetyhing and changed my config/application.rb to test those settings and them the error appeared

Checklist

• Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
• Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.boltops.com
• Code sample: Have you put together a code sample to reproduce the issue and make it available? Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.

My Environment

Software	Version
Operating System
Jets
Ruby

---

Expected Behaviour

Current Behavior

Step-by-step reproduction instructions

Code Sample

Solution Suggestion

[tongueroo]

Thanks for reporting. So, one of the reasons I did not document those options, one_lambda_per_controller and one_apigw_method_per_route, because they are going to be removed in the future. It also has some quirks that didn’t have time to fix. It’s a bit of effort to support both. Would like to remove them. It’s one of the reasons why I didn’t document it yet.

Related: https://community.boltops.com/t/ruby-on-jets-5-0-release-improvements-galore/1123/17?u=tung

Also, Jets 6.0 is going to work a lot different from Jets 5.0. If you can, suggest waiting for it. It's probably at least a month out though. Hope that helps 👍