charlotte 🌸

Thanks for looking into this @silasdavis!

@bradfitz Sorry to ping you, but looks like you were the last person to merge a PR on this repo. Is it possible you could take a look at this?...

I'm hoping to find some time over the holidays to take the work @silasdavis did and migrate it into the appropriately versioned module.

This happened to me because I failed to init the ssh agent and ssh-add. Doing so solved my problems. :)

Yup, bad example on my part--should have copied the offending code directly from my sketch: properly spacing the infix operator solves the problem, it's only when there is no whitespace...

@bacongobbler This broke some stuff for us. I'd be interested in working on a PR, however it seems non-trivial, so I'd like to check the approach. It looks like `gopkg.in/yaml.v3`...

@sreya92 Got busy at work. Here's where I left off: switching to yaml.v3 was mostlyeasy, with the exception of [this bit here](https://github.com/helm/helm/blob/master/pkg/chartutil/jsonschema.go#L63). Wasn't sure what the best approach to handle...

Opened https://github.com/ghodss/yaml/issues/61 to inquire about possibility of an upgrade path there. Will wait to hear back from them before continuing anything else -- upgrading dependencies is way preferable to other...

Hi @johnward -- it's my intention to publish the protocol codegen as it's own crate. The primary thing blocking that right now is getting this merged upstream: https://github.com/carllerche/string/pull/27.

Same issue on EKS. Deleting state resources one by one (these mostly cluster resources that had been cleaned up) and verifying their deletion in AWS console was able to resolve.