I kinda gave up on SAM a while back because of the lack of configuration possibilities. Now though you can for example !Ref Stage & !Ref Deployment and configure MethodSettings! Maybe I'll give SAM another try!https://twitter.com/chrismunns/status/973570150116012032 …
-
-
-
Replying to @chrismunns @aripalo
Ignore the lack of plugins which makes SLA my choice over SAM.... Both SAM and SLS lack the ability to group configuration resources together and in a reusable manner. Ex. SQS queue + CloudWatch alarms so every time I deploy an SQS queue I have some monitoring.
1 reply 0 retweets 0 likes -
Replying to @tmclaughbos @aripalo
i am not sure of something that does that today on AWS in general. Feels like more of a CloudWatch gap for "auto-alarms" or something similar. Alarm Rules? IDK. worth digesting further though
4 replies 0 retweets 0 likes -
"auto-alarms" sound super cool! I also like Tom's idea of an alarm module/template for all resources. Captured everything and created a RFC in SAM Github repo to gather feedback - https://github.com/awslabs/serverless-application-model/issues/334 … - Go cast your votes now!
1 reply 0 retweets 3 likes -
Give me the ability to create repeatable configuration and that will be far more powerful to me than trying to make the DSL handle every possible combination of feature ideas. With some form of module concept I can extend configuration quickly and easily with existing resources.
2 replies 0 retweets 1 like -
Replying to @tmclaughbos @sanathkr_ and
FWIW, I think the trend towards simplicity in infra tooling as a reaction to complaints about the complexity of Puppet and Chef were terribly misguided. I loved the expressiveness of those DSLs and have always wished for similar for handling AWS infrastructure. :)
1 reply 0 retweets 2 likes
Ya may want to check out what @PulumiCorp are up to
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
CORS Support