| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The insync? method wasn't accounting for a condition where the state was
absent and the desired state was absent. This manifest itself in puppet
runs that would constantly output the following after setting
ensure => absent.
2016-09-01T16:39:27.314283+00:00 vcstest puppet-agent[1161]: (/Stage[main]/Main/Node[vcstest]/Vcsrepo[/home/vagrant/test]/ensure) created
2016-09-01T16:40:22.583125+00:00 vcstest puppet-agent[1727]: (/Stage[main]/Main/Node[vcstest]/Vcsrepo[/home/vagrant/test]/ensure) created
2016-09-01T16:41:04.031750+00:00 vcstest puppet-agent[2267]: (/Stage[main]/Main/Node[vcstest]/Vcsrepo[/home/vagrant/test]/ensure) created
2016-09-01T16:42:51.779816+00:00 vcstest puppet-agent[2911]: (/Stage[main]/Main/Node[vcstest]/Vcsrepo[/home/vagrant/test]/ensure) created
2016-09-01T16:43:42.189035+00:00 vcstest puppet-agent[3466]: (/Stage[main]/Main/Node[vcstest]/Vcsrepo[/home/vagrant/test]/ensure) created
I added unit tests for the vcsrepo type and then fixed the code.
|
|
|
|
|
|
Example:
vcsrepo { '/path/to/repo':
ensure => mirror,
provider => git,
source => 'git://example.com/repo.git',
}
|
|
this will stop failing in case there is a tag which is a substring of an existing branch name.
for example if there is a tag 'release' and a branch 'release/integration' current code will match 'release/integration' with pattern 'release' and decide that a branch checkout is needed. but release branch does not exist so it will fail.
this simple fix resolves the issue.
|
|
false is not a valid value; only :false is.
|
|
Autorequire Package['mercurial']
|
|
added param trust server cert
updated depth feature
updated README.markdown
trust_server_cert is not feature
trust_server_cert default value should be false
add test for depth and trust_server_cert
|
|
Explitly unset SSH_AUTH_SOCK; it is preferred to the -i flag
|
|
|
|
The URL can have special characters, making the regex match fail.
|
|
Along the lines of 2b190756260346931b8f9a0dda8afc0c815710d6, if the
Mercurial package is being managed, it stands to reason that the Mercurial
package should be installed before trying to potentially manage Mercurial
repositories using vcsrepo resources.
This commit adds an autorequire to the vcsrepo type that reflects the
above premise.
|
|
Will also work with empty repositories.
|
|
This would explode when revision was unspecified when you were on a
branch. Use the branch you're currently on when updating.
|
|
Even if the -i flag is explicitly passed via the command line, openssh
ignores the identity file if an socket exists to an SSH authentication
agent. In cases where puppet has been configured to use an explicit
identity file, altering behavior based on the calling environment of
puppet violates the principle of least surprise, and can lead to
inconsistent deployments.
Work around this odd corner case of ssh by explicitly unsetting
SSH_AUTH_SOCK inside the ssh wrapper.
|
|
|
|
MODULES-2131 Git provider now takes account of revision property when using depth property.
|
|
depth property.
|
|
Consider the submodules flag on specific revision cloning
|
|
Very often /tmp is mounted noexec for security reasons related to it
being writable by all users. This stopped vcsrepo's git provider from
working.
This pull request uses puppet's statedir as it is not writable by all
users and is a good candidate for transient state like the git
provider's identity script for the $GIT_SSH command.
An alternative in the future that wouldn't require a temporary file is
to set $GIT_SSH_COMMAND instead of $GIT_SSH, except this was added in
git 2.3 and is too new to depend on.
|
|
Shallow clone with one commit that corresponds to arbitrary tag from arbitrary branch
|
|
Add support for 'conflict' parameter to populate svn --accept arg
|
|
Without this commit, the unit tests for the git provider changing
multiple remotes mocks the remotes in a particular order. While in
practice it doesn't matter which remote the update_remotes method
updates first, the unit tests must be able to mock them in the correct
order. For ruby 1.8.7, a Hash will not necessarily produce key value
pairs in the same order on each run, which causes intermittent failures
in the unit tests. This change sorts the :source property values before
trying to update them, and updates the unit tests to expect the values
in alphabetical order.
|
|
|
|
|
|
|
|
|
|
|
|
Add submodules feature to git provider
|
|
|
|
The `retrieve` method was calling `create` and `destroy` on every run
with `force => true`. Retrieve should not be making any changes to the
system, so removed that code, and updated `working_copy_exists` to make
sure that the directory not only contains a `.git` directory, but also
if `source` is specified it also matches `#{path}/.git/config` so that
it will overwrite a git repo with a different source.
Updated tests to not check for the old broken behavior. Added a regression test.
|
|
The "format" entry in a SVN directory is a file, not a directory.
|
|
|
|
|
|
Change uid by Puppet execution API
|
|
Thanks to @revhazroot for identifying the problem that excludes with a
string or single-element array fails on Ruby >= 1.9.
|
|
|
|
Puppet started raising a warning about multiple default providers due to
a change in puppet. The dummy provider exists to raise an error when
`provider` is not specified because there is no way to declare
`provider` as a required attribute in the type. Even passing a
`provider` value did not get rid of the "multiple default providers
found" warning however.
This commit causes the dummy provider to be the defacto default for all
resources which do not have an explicit provider declared, as the posix
feature is available on basically every operating system on which
vcsrepo works. (There is no way to create an "always default" provider.)
|
|
|
|
Update Markdown with missing Perforce details.
|
|
Previously vcsrepo detached HEAD on checkout which caused further branch
revisions to fail. This corrects the behavior, and works on git 1.7,
1.8, 1.9, and 2.0
|
|
Fix tabs/spaces in p4.rb
|
|
Basic Perforce provider
|
|
Fix issue with node changing every checkin
|
|
|
|
Update noop to work
|
|
|
|
Keys in the Client spec were processed out of order and failing tests.
|
|
|
