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
This is an interesting idea but something jumped out at me. maybe that's because i don't know all the details of how serverless compiles my yamls before it sends to CF.
The reason it worried me a bit is because when we do cicd, we'll have to manage pulling the parent(s) repos, and branches + automation tests might get harder to manage, since these seem to literally use the yaml files in parent directories instead of checking CF or looking in a bucket or something like that.
it's possible this isn't a problem if:
Serverless doesn't compile CF templates on my machine. instead it does it from a bucket or something like that.
Serverless doesn't require the parent directory to be at some path on the same server it runs a deploy from.
The text was updated successfully, but these errors were encountered:
This is an interesting idea but something jumped out at me. maybe that's because i don't know all the details of how serverless compiles my yamls before it sends to CF.
The reason it worried me a bit is because when we do cicd, we'll have to manage pulling the parent(s) repos, and branches + automation tests might get harder to manage, since these seem to literally use the yaml files in parent directories instead of checking CF or looking in a bucket or something like that.
it's possible this isn't a problem if:
Serverless doesn't compile CF templates on my machine. instead it does it from a bucket or something like that.
Serverless doesn't require the parent directory to be at some path on the same server it runs a deploy from.
The text was updated successfully, but these errors were encountered: