You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 7, 2020. It is now read-only.
Do you think if we run "sam init" in one of the cloud-api backend folders that we could get a backend api up and running in SAM without the need to push it to with awsmobile push in order to test?
If so, will it mess up the awsmobile push? Like cause a corruption that would cause CloudFormation to run in an infinite loop causing the need to destroy the stack and restart from scratch?
The text was updated successfully, but these errors were encountered:
AWS said, "No".
But, I thought I'd ask here anyway.
Do you think if we run "sam init" in one of the cloud-api backend folders that we could get a backend api up and running in SAM without the need to push it to with awsmobile push in order to test?
If so, will it mess up the awsmobile push? Like cause a corruption that would cause CloudFormation to run in an infinite loop causing the need to destroy the stack and restart from scratch?
The text was updated successfully, but these errors were encountered: