<story><title>AWS Copilot</title><url>https://aws.amazon.com/blogs/containers/introducing-aws-copilot/</url></story><parent_chain><item><author>realharo</author><text>I feel like trying to use a &amp;quot;dumb&amp;quot; declarative config language for everything is part of the problem.&lt;p&gt;The domain is not simple enough for that, so you end up with all kinds of weird scripts around it all, or other templating&amp;#x2F;codegen solutions, plus all kinds of ad-hoc conventions that are extremely easy to break and very annoying to navigate.&lt;p&gt;Having a full blown statically typed language like TypeScript - where things can reference each other strongly (not just by names and other strings), naming conventions can be encoded in functions (or even enforced by types), and structures on &lt;i&gt;every&lt;/i&gt; level (even your project-specific ones) have a well-defined and checked schema - would help a lot in my opinion.&lt;p&gt;Maybe deno could find a use in this niche.</text></item><item><author>noisy_boy</author><text>Not directly related to copilot but in context of ever increasing yml&amp;#x2F;json configurations for cloud apps, am I the only one who feels overwhelmed with the configuration options? I see tons of articles with just drop this json here and that yml there and run this cli command - where is the reference for these json&amp;#x2F;ymls? Does everyone fully know&amp;#x2F;understands the structure&amp;#x2F;options? How do people keep track of the changes to that between upgrades? I feel increasingly dumb the more I see these configs.</text></item></parent_chain><comment><author>scrollaway</author><text>You&amp;#x27;re (accidentally, I think?) describing Pulumi in striking detail.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.pulumi.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.pulumi.com&amp;#x2F;&lt;/a&gt;</text></comment>
<story><title>AWS Copilot</title><url>https://aws.amazon.com/blogs/containers/introducing-aws-copilot/</url></story><parent_chain><item><author>realharo</author><text>I feel like trying to use a &amp;quot;dumb&amp;quot; declarative config language for everything is part of the problem.&lt;p&gt;The domain is not simple enough for that, so you end up with all kinds of weird scripts around it all, or other templating&amp;#x2F;codegen solutions, plus all kinds of ad-hoc conventions that are extremely easy to break and very annoying to navigate.&lt;p&gt;Having a full blown statically typed language like TypeScript - where things can reference each other strongly (not just by names and other strings), naming conventions can be encoded in functions (or even enforced by types), and structures on &lt;i&gt;every&lt;/i&gt; level (even your project-specific ones) have a well-defined and checked schema - would help a lot in my opinion.&lt;p&gt;Maybe deno could find a use in this niche.</text></item><item><author>noisy_boy</author><text>Not directly related to copilot but in context of ever increasing yml&amp;#x2F;json configurations for cloud apps, am I the only one who feels overwhelmed with the configuration options? I see tons of articles with just drop this json here and that yml there and run this cli command - where is the reference for these json&amp;#x2F;ymls? Does everyone fully know&amp;#x2F;understands the structure&amp;#x2F;options? How do people keep track of the changes to that between upgrades? I feel increasingly dumb the more I see these configs.</text></item></parent_chain><comment><author>codebeaker</author><text>It sounds like you&amp;#x27;re describing HashiCorp&amp;#x27;s HCL2 and Terraform Configs which are at least a &lt;i&gt;graph&lt;/i&gt;.&lt;p&gt;I find using AWS without Terraform to be nearly impossible.</text></comment>