Bug: nested stack sam sync Config file does not exist or could not be read

[jchirschy]

In a nested stack, synccommand doesn't not seem to work when using --config-file option. The same option works very well with the command build specifying the same path and running the cli from the same path.

[jysheng123]

Hi, thanks for bringing up the issue. There's a lot more information that I need to know about you environment to triage your issue properly. Could you run sam --info and let me know your output. Also I need more context on the sam project that is failing in general. Is there anything unique to your config-file compared to the default samconfig.toml used. What kind of template are you running for the nested stack? Ideally, if you could provide a sample project that recreated the same error that would be great. If it is not possible, I would need more details for example the output of sam sync --debug --config-file <config file>, especially at the part where the failure occurs.

[mildaniel]

Closing due to inactivity. If the issue persists, please open a new issue.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.