Hi,
I''ve been playing with the vcsrepo type and for the most part it works
pretty well, with the exception of ensure => latest/present with svn...
when I ensure => present, it does what I expect, creates the working
directory at whatever version the repo is currently at, and leaves it alone
thereafter. However, when I use "ensure => latest" unless the
working
directory exists as a SVN repo, it fails. Shouldn''t "ensure =>
latest" imply
"ensure => present" ? I started down the road of writing something
to
ensure a created working directory, and thought I''d bounce it off the
list
to see if anyone else had any experience with vcsrepo, since it''s
entirely
possible that I''ve missed something blindly obvious.
vcsrepo { "/path/on/disk":
ensure => latest,
provider => svn,
source =>
''https://server.example.com/repo/trunk/apps/foo'',
}
Thanks! And thanks to whomever wrote this type, it''s going to be super
useful!!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Alaric, I''ve just made a fix to the svn provider (and a related tidy up to the vcsrepo type) That change is available at: http://github.com/mikeknox/puppet-vcsrepo Cheers On 17/09/10 5:44 AM, Alaric wrote:> Hi, > > I''ve been playing with the vcsrepo type and for the most part it works > pretty well, with the exception of ensure => latest/present with > svn... when I ensure => present, it does what I expect, creates the > working directory at whatever version the repo is currently at, and > leaves it alone thereafter. However, when I use "ensure => latest" > unless the working directory exists as a SVN repo, it fails. Shouldn''t > "ensure => latest" imply "ensure => present" ? I started down the > road of writing something to ensure a created working directory, and > thought I''d bounce it off the list to see if anyone else had any > experience with vcsrepo, since it''s entirely possible that I''ve missed > something blindly obvious. > > vcsrepo { "/path/on/disk": > ensure => latest, > provider => svn, > source => ''https://server.example.com/repo/trunk/apps/foo'', > } > > > Thanks! And thanks to whomever wrote this type, it''s going to be super > useful!! > > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Michael,
Thanks for the response! Thats awesome! I updated vcsrepo, and got it
doing essentially what I expected, puppet did complain a bit that it
didn''t know the state of the resource if the directory didn''t
exist,
so I had puppet create the directory before running vcsrepo
file { "/path/to/workingcopy":
ensure => directory,
}
vcsrepo { "/path/to/workingcopy":
ensure => latest,
provider => svn,
source =>
''https://foo.example.com/repo/trunk/path/to/repo'',
require => File["/path/to/workingcopy"],
}
Thanks again for all the help!
Best,
-a
On Sep 16, 7:39 pm, Michael Knox <michael.knox...@gmail.com>
wrote:> Alaric,
> I''ve just made a fix to the svn provider (and a related tidy up to
the
> vcsrepo type)
> That change is available at:http://github.com/mikeknox/puppet-vcsrepo
>
> Cheers
>
> On 17/09/10 5:44 AM, Alaric wrote:
>
> > Hi,
>
> > I''ve been playing with the vcsrepo type and for the most part
it works
> > pretty well, with the exception of ensure => latest/present with
> > svn... when I ensure => present, it does what I expect, creates
the
> > working directory at whatever version the repo is currently at, and
> > leaves it alone thereafter. However, when I use "ensure =>
latest"
> > unless the working directory exists as a SVN repo, it fails.
Shouldn''t
> > "ensure => latest" imply "ensure => present"
? I started down the
> > road of writing something to ensure a created working directory, and
> > thought I''d bounce it off the list to see if anyone else had
any
> > experience with vcsrepo, since it''s entirely possible that
I''ve missed
> > something blindly obvious.
>
> > vcsrepo { "/path/on/disk":
> > ensure => latest,
> > provider => svn,
> > source =>
''https://server.example.com/repo/trunk/apps/foo'',
> > }
>
> > Thanks! And thanks to whomever wrote this type, it''s going to
be super
> > useful!!
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Puppet Users" group.
> > To post to this group, send email to puppet-users@googlegroups.com.
> > To unsubscribe from this group, send email to
> > puppet-users+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.