Zoltán Reegn

https://github.com/awslabs/amazon-eks-ami/pull/587 reverted this change earlier, now that eksctl was made compatible with this change in https://github.com/weaveworks/eksctl/pull/2962 it should be OK to merge again.

This is another run at https://github.com/awslabs/amazon-eks-ami/issues/490

@abeer91 I do understand the concern of breaking downstream tooling, so I might look into how that could be handled, although I can't promise anything (thinking about maybe using a...

> We emphatically do not support older versions of eksctl. If users are running any version of eksctl which is not latest, they are doing it wrong 🙃 . @Callisto13...

@stevehipwell Legacy flow seems to be supported for Custom AMIs, not the official EKS AMI, for the official EKS AMI they use the /etc/eks/bootstrap.sh, no legacy code-path there. We're talking...

Same on my side, but for github enterprise. I could bootstrap the repo with github-enterprise by using `--provider=github`, but I cannot create a project.

I'm also seeing the same issue with v0.3.1. I have `master` as the defaultBranch set in `.gitconfig` for backward-compatibility reasons, and this is causing a problem for me.

I ran into this issue as well... And nope, yamlbeans doesn't support the merge syntax: https://github.com/EsotericSoftware/yamlbeans/blob/master/src/com/esotericsoftware/yamlbeans/tokenizer/Tokenizer.java#L259 Why doesn't this plugin use snakeyaml? It's basically the best yaml parser for java...

Hi @tomzo, I was simply surprized that it didn't use snakeyaml since everywhere you see snakeyaml when you run into yaml parsing in java (eg. https://github.com/FasterXML/jackson-dataformat-yaml). :) I am pretty...

So is yamlbeans. Checked the code, still using yamlbeans for parsing the config.