Can't deploy 'key not found: :ciphers'

[benlieb]

I can't deploy using the ey command:

$ ey deploy -e myapp
Loading application data from Engine Yard Cloud...
key not found: :ciphers

engineyard version 3.2.5
ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-darwin18]

[ess]

Hi @benlieb !

Realizing that it's been a good while since you submitted this report, we're currently working through the backlog of both internal and user-submitted issues for this gem.

If I might, is this behavior still persisting? If so, have you tried any newer versions of the gem (the current release is v3.5.0)?

[benlieb]

Somewhere along the line I solved the problem but I don't quite remember how. I think it had to do with SSH versions, and confusion with ey and ey-core. I might as well take the opportunity to say that working with ey and ey-core has been quite unpleasant. The documentation for ey-core and ey is bad and/or hard to find and/or non-existent. To be honest if I were the person making the decisions on our team about what services to use, I would leave Engine Yard.

[ess]

Hey @benlieb

Somewhere along the line I solved the problem but I don't quite remember how. I think it had to do with SSH versions, and confusion with ey and ey-core. I might as well take the opportunity to say that working with ey and ey-core has been quite unpleasant. The documentation for ey-core and ey is bad and/or hard to find and/or non-existent. To be honest if I were the person making the decisions on our team about what services to use, I would leave Engine Yard.

I had two off-the-cuff thoughts when I read that message, and it's my hope that at least one of them surprises you:

• You're not wrong. There are a lot of headaches involved with using our platform and the tools around it, and our docs could be generously described as "a bit lacking." I use the platform every day. Believe me, I hear you.
• It seems like you're exactly who I need to talk to, in so far as I'm one of the handful of folks that have recently been tasked with combing over the platform, docs, and related tools to try to at least lower the number of headaches that we cause.

I'm cautiously optimistic that we're going to do a pretty good job, but I'm curious if you'd mind if I were to reach out privately (like, via a helpdesk ticket or something) so we can have a more in depth conversation about the sorts of headaches you run into.

That cool with you?

[benlieb]

@ess Thanks for the thoughtful reply. I'd be happy to, and maybe another person on my team might be interested in joining.