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

[LOVE] exec resource needs a refreshonly-like option #464

Open
ffrank opened this issue Feb 6, 2019 · 3 comments
Open

[LOVE] exec resource needs a refreshonly-like option #464

ffrank opened this issue Feb 6, 2019 · 3 comments

Comments

@ffrank
Copy link
Contributor

ffrank commented Feb 6, 2019

Versions:

  • mgmt version (eg: mgmt --version): 0.0.17

  • operating system/distribution (eg: uname -a): any

  • golang version (eg: go version): 1.10

Description:

With the goal of enabling Puppet code to run through mgmt, it will be necessary to implement the refreshonly semantics in exec resources. This means that the resource will never sync on its own, and only take action when receiving refresh events. A parameter should toggle this mode for each resource.

@roidelapluie
Copy link
Contributor

we also need a "time period" before doing the refresh.

it is not rare that a checkapply happens multiple times in very short time period.

I would like to see a "quiet_period" parameter added to the refreshonly.

@purpleidea
Copy link
Owner

@ffrank In this case, I assume the idea is to never receive any events, so no Watch() behaviour then?

I'm okay with this patch, maybe we should call it Refresh?

@roidelapluie Can you expand on your time period idea please? Are you should you aren't interested in the already existing limit and burst metaparams?

@purpleidea
Copy link
Owner

@peckpeck I think this is what you were interested in. Perhaps you want to describe the "don't run on first run without notification" feature.

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

No branches or pull requests

3 participants