Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify transport type #405

Closed
wants to merge 29 commits into from
Closed

Conversation

thanandorn
Copy link

It would be nice if we could specify transport type even only for testing.

Thanks,
Tron

@thanandorn thanandorn closed this Aug 30, 2015
@thanandorn
Copy link
Author

Redis transport seems to be supported officially now so re-open this.

@thanandorn thanandorn reopened this Dec 6, 2015
bovy89 and others added 24 commits December 6, 2015 23:48
This problem doesn't always happen.  I'm unable to reproduce when
just declaring class {'sensu':} by itself.  However, it does seem
to happen when declared in a profile with other classes that use
puppetlabs-apt.  My best guess is that once one of the other
classes triggers an apt-get update, another one doesn't happen
within the same run.  In any case, the official puppetlabs-apt
docs now state that one's package resource must have an explicit
dependency on class apt::update if you expect things to work in one
run:
https://github.com/puppetlabs/puppetlabs-apt#adding-new-sources-or-ppas

Change-Id: I14ff923ec87cc45f4e845d043b4bf7fca7e11c00
the run fails on centos/redhat when strict_variables is enabled
Readding accidentally removed config options

Fixing whitespace
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants