On Aug 24 13:56, Karanbir Singh wrote:
On 22/08/17 03:55, Brian Stinson wrote:
If you have a feature request for us to track let's talk about it here.
been thinking through creds a bit this morning.
Duffy already sets up the user / label key so that the jobs can ssh into the remote host and do what they need to do. I am wondering if we can extend this to also cover other credentials that jobs might need. and plug in something like hash vault that then allows users to self-manage their creds, and have them auto available in the sessions on the remote hosts.
as an example, something extremely simple, like a key value file, sourced in the .bashrc of the remote shell would give you whatever is labelled for the tenant, in place.
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Are there specific developers asking for this? Who is best to help us with the acceptance criteria?
I don't want to go too far down the implementation path for this until we know what they need. That will also help answer the question of if Duffy is the right place for this.