On Thu, Sep 11, 2014 at 6:18 AM, Juan Andres Ramirez
wrote:
> Hello,
>I have data in machine.yaml :
>
> sitedefinition:
> - website: "site.one.com"
> ipadress: "192.168.0.2"
> protocol: "http"
> port: "80"
> - website : "site.two.com"
> ipadress : "192.
On Wed, Sep 17, 2014 at 12:00 PM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> [snip]
>
> There are other exciting cases in there, such as "is a resource failed
> if it's in sync but the refresh fails" and so forth. I feel that those
> are more relevant, but should probably be handled o
On Wednesday, September 17, 2014 12:12:31 PM UTC-5, Andy Parker wrote:
>
> Adrien has put together a change to address PUP-1106 (failed dependencies
> are not honored on refresh), however this is a really thorny issue and I'd
> like to get some more eyes on it before committing to the change.
>
On 09/17/2014 07:12 PM, Andy Parker wrote:
> Adrien has put together a change to address PUP-1106 (failed
> dependencies are not honored on refresh), however this is a really
> thorny issue and I'd like to get some more eyes on it before
> committing to the change.
>
> I think the original bug in r
I think I'm in favor of this. I can imagine some case where this isn't the
behavior you want, but it has a major advantage over any other behavior:
it's explainable and intuitive. Behaving predictably is a feature!
--
You received this message because you are subscribed to the Google Groups
"P
Adrien has put together a change to address PUP-1106 (failed dependencies
are not honored on refresh), however this is a really thorny issue and I'd
like to get some more eyes on it before committing to the change.
I think the original bug in redmine has the most history (
http://projects.puppetla
Sorry for the late notice, but Ethan and I are both working hard on our
PuppetConf talks. As always, feel free to ping one of us on IRC re any PRs
in flight or other questions.
And looking forward to seeing some of you next week in SF!
Kylo
--
Kylo Ginsberg
k...@puppetlabs.com
*Join us at **Pu
