[ 
https://issues.apache.org/jira/browse/WHIRR-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550418#comment-13550418
 ] 

Guido Serra aka Zeph commented on WHIRR-688:
--------------------------------------------

it is not elegant (the password ends up in the /tmp/ scripts on the nodes), but 
it works!

...regarding the issue with the "--non-interactive" ...I was passing the wrong 
svn password :(

                
> svn credentials support, in particular for puppet's recepies checkout
> ---------------------------------------------------------------------
>
>                 Key: WHIRR-688
>                 URL: https://issues.apache.org/jira/browse/WHIRR-688
>             Project: Whirr
>          Issue Type: New Feature
>          Components: service/puppet
>    Affects Versions: 0.8.1
>            Reporter: Guido Serra aka Zeph
>            Assignee: Tom White
>              Labels: puppet, svn
>         Attachments: auth.patch, svn.patch
>
>
> all seems to be designed to work either with a tar.gz to be downloaded
> either with an anonymous git repository... 
> in my case, I'd need to provide a URL of an svn repository, and ask 
> interactively to the user his/her credentials for the svn
> the specific usecase is when using the puppet integration, 
> I need to enable the component to download my recepies
> and maybe even reuse these credentials from within the puppet scripts
> for the time of execution of whirr itself... (without leaving trace of them 
> to a user that is going to login afterwards to the node)
> p.s. I wonder how to name the svn url, as http :// seems to be handled by 
> default by curl, and svn:// is not svn over http, 
> it is a completely different protocol (and svn+http ://, thinking of 
> svn+ssh://, is not a registered protocol either) ...suggestions?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to