Closed sferich888 closed 8 years ago
cc: @oybed @sabre1041 @timothyh
So here's my opinion on how we move this forward.
MVP (1st merge):
Future State:
@sferich888 do you want to handle the first set of items or should one of us take this over?
We should not hard code 2048 as the bit count and we should go a step further by requiring a strong password on PEM creation.
Feel free to take over I will contribute where I can. On Jun 21, 2016 10:28 AM, "Eric Sauer" notifications@github.com wrote:
@sferich888 https://github.com/sferich888 do you want to handle the first set of items or should one of us take this over?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rhtconsulting/rhc-ose/pull/188#issuecomment-227457374, or mute the thread https://github.com/notifications/unsubscribe/ABUZmoe2eBlhK9YR9zk0f2nXeQzAv7qgks5qN_UogaJpZM4I4vo0 .
This has been moved out to its own repo: https://github.com/rhtconsulting/ocp-watcher-skel
Closing
Closing per above comment
@etsauer can you look at this, its a bit rough, and will likely need some TLC. It all works, except for the add certificate (patch route) the proxy throws an error, that the certificate is formatted badly.