Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Copilot

aws.amazon.com

Post reply on HN
Print view View original

61–70 of 97 posts

Re: AWS Copilot

#61

Post by luisfmh »

leokennis wrote: post #44
noisy_boy wrote: post #36

Not directly related to copilot but in context of ever increasing yml/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/ymls? Does everyone fully know/understands the structure/options? How do people keep track of the changes…

Oof yes. The times I read stuff like "to make sure your WidgyPidy will automatically balance your BoolyPooly cluster, just set the autoEnableBalanceBoolyClusterGenerated in your WiPoBaClConfig.yml file to the desired floating point and drop a reference in the ServerClusteringPoolDirective.json in your configured ShimpyDimpy config folder" like it's obvious and simple...

This starts to sound more and more like how they manufacture plumbuses

Re: AWS Copilot

#62

Post by joshxyz »

leokennis wrote: post #44
noisy_boy wrote: post #36

Not directly related to copilot but in context of ever increasing yml/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/ymls? Does everyone fully know/understands the structure/options? How do people keep track of the changes…

Oof yes. The times I read stuff like "to make sure your WidgyPidy will automatically balance your BoolyPooly cluster, just set the autoEnableBalanceBoolyClusterGenerated in your WiPoBaClConfig.yml file to the desired floating point and drop a reference in the ServerClusteringPoolDirective.json in your configured ShimpyDimpy config folder" like it's obvious and simple...

This is just.. accurate.

Re: AWS Copilot

#63

Post by stjo »

luisfmh wrote: post #61
leokennis wrote: post #44

Earlier quoted context omitted.

Oof yes. The times I read stuff like "to make sure your WidgyPidy will automatically balance your BoolyPooly cluster, just set the autoEnableBalanceBoolyClusterGenerated in your WiPoBaClConfig.yml file to the desired floating point and drop a reference in the ServerClusteringPoolDirective.json in your configured ShimpyDimpy config folder" like it's obvious and simple...

This starts to sound more and more like how they manufacture plumbuses

High IQ joke

Re: AWS Copilot

#64

Post by realharo »

scrollaway wrote: post #54
realharo wrote: post #48

Earlier quoted context omitted.

I feel like trying to use a "dumb" declarative config language for everything is part of the problem. The domain is not simple enough for that, so you end up with all kinds of weird scripts around it all, or other templating/codegen solutions, plus all kinds of ad-hoc conventions that are extremely easy to break and very annoying to navigate. Having a full blown statically typed language like TypeScript - where thing…

You're (accidentally, I think?) describing Pulumi in striking detail. https://www.pulumi.com/

Kind of. From a brief look, it looks very framework-y and all-or-nothing (though I could be wrong, they do have a page about gradual adoption at least https://www.pulumi.com/docs/guides/adopting/).

I was picturing something more low level and less opinionated, though I can only guess how such a thing would perform in practice.

Not even necessarily a specific product, just the adoption of workflows that use already existing tools (e.g. the various API client libraries - for AWS, Kubernetes, git, docker registry, etc.) to achieve this. I realize that that could lead to reinventing the wheel, and eventually an in-house framework anyway, but it feels a lot more comfortable to start there, as you can design things closer to your exact needs.

Pulumi definitely looks interesting though.

Re: AWS Copilot

#65

Post by jeremya »

drej wrote: post #55

I probably missed it in the blogpost and github readme, but is there a good way to "export" this into a CloudFormation/Terraform template? After all, this seems to spawn a few things (networking, mostly), so I want to make sure I can automate any further deployments. Thanks!

Copilot generates CloudFormation templates based on the Copilot-specific config files. There’s a place where you can add your own additional resources in CloudFormation syntax IIRC. It also has the ability to create a CodePipeline for app deployment. That creation is also done by generating a CloudFormation template and deploying it for the user. I’m not sure why it’s not clearly documented that this is happening, but it is a selling point to me because if I want to, I can “eject” from Copilot and just maintain/enhance the CloudFormation templates.

Re: AWS Copilot

#66

Post by leetrout »

luisfmh wrote: post #61
leokennis wrote: post #44

Earlier quoted context omitted.

Oof yes. The times I read stuff like "to make sure your WidgyPidy will automatically balance your BoolyPooly cluster, just set the autoEnableBalanceBoolyClusterGenerated in your WiPoBaClConfig.yml file to the desired floating point and drop a reference in the ServerClusteringPoolDirective.json in your configured ShimpyDimpy config folder" like it's obvious and simple...

This starts to sound more and more like how they manufacture plumbuses

I always wondered how plumbuses got made.

Re: AWS Copilot

#67

Post by moltar »

realharo wrote: post #48
noisy_boy wrote: post #36

Not directly related to copilot but in context of ever increasing yml/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/ymls? Does everyone fully know/understands the structure/options? How do people keep track of the changes…

I feel like trying to use a "dumb" declarative config language for everything is part of the problem. The domain is not simple enough for that, so you end up with all kinds of weird scripts around it all, or other templating/codegen solutions, plus all kinds of ad-hoc conventions that are extremely easy to break and very annoying to navigate. Having a full blown statically typed language like TypeScript - where thing…

Have you seen aws-cdk or pulumi? Does exactly that with TypeScript to boot :)

Re: AWS Copilot

#68

Post by billman »

kohidavez wrote: post #4

Hi!! I’m a developer on AWS Copilot! We’d love your feedback! Homebrew: brew install aws/tap/copilot-cli Docs: https://aws.github.io/copilot-cli/ Feedback & Requests: https://github.com/aws/copilot-cli/issues/new

Do you know if EKS will ever be supported?

Re: AWS Copilot

#69

Post by ghaff »

noisy_boy wrote: post #36

Not directly related to copilot but in context of ever increasing yml/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/ymls? Does everyone fully know/understands the structure/options? How do people keep track of the changes…

And get the second order effect of one of those configuration options wrong and wake up to a huge AWS bill. And, yes, with a bit of groveling they'll probably refund you after you've sweated a bit--the first time at least.

Re: AWS Copilot

#70

Post by omni »

zelly wrote: post #17
kohidavez wrote: post #4

Hi!! I’m a developer on AWS Copilot! We’d love your feedback! Homebrew: brew install aws/tap/copilot-cli Docs: https://aws.github.io/copilot-cli/ Feedback & Requests: https://github.com/aws/copilot-cli/issues/new

Remove the emojis please

Counter-opinion: I think they do a good job of visually distinguishing the section headers in the help output. As long as they're used structurally like that, I think they're great.
Post reply on HN