Remove "patron" hint from the AWS guide #277
Conversation
because using Patron is not a prerequisite when using this workflow, and might in fact mislead the user to installing Patron and adding it to his Gemfile just because this is mentioned in the documentation
|
Yes, correct, nice catch. May I ask you to sign the CLA so I can merge the contribution, please? (I know it looks silly to require CLA for a one line change in README, but it's the easiest and fastest way for us to process contributions...) |
|
I did sign the CLA, but I never got the confirmation email about it (me at julik dot nl). I can also bike by your office and sign it in person, but only if you give me a cup of espresso in exchange ❤️ |
Hi Julik, that is weird! Would be so kind and tried again? Maybe there's some kind of problem we need to debug -- I don't see you in our records indeed.
I'm about 900km from there, but I can arrange a cup of espresso -- not terribly great, warn you :) I'm afraid, though, that we still need the signature in the systems, so the whole toolchain knows about you :) |
|
I have resubmitted the CLA |
|
Perfect, thanks!, tweaked the commit message a little bit and merged. |
…nstrumentation) Fixes elastic#277 Closes elastic#278
because using Patron is not a prerequisite when using this workflow, and might in fact mislead
the user to installing Patron and adding it to his/her Gemfile just because this is mentioned in the documentation.