-
Notifications
You must be signed in to change notification settings - Fork 282
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
State postgres-reload-modules always reports changes #214
Comments
alxwr
added a commit
to alxwr/postgres-formula
that referenced
this issue
Apr 30, 2019
…formulas#214 Based on the great work of @RobRuana in saltstack-formulas#216.
alxwr
added a commit
to alxwr/postgres-formula
that referenced
this issue
May 3, 2019
…formulas#214 Based on the great work of @RobRuana in saltstack-formulas#216.
jerrykan
added a commit
to jerrykan/postgres-formula
that referenced
this issue
Sep 8, 2021
…ormulas#214) We don't want the `postgres-reload-modules` state reporting any changes to the user unless there is a need to reload the modules. We should only need to reload the modules if the state that manages installing the client libraries makes any changes (ie. new packages installed). In turn, the states created by the `format_state` macro only need to ensure that any module reload occurs before those states are applied. In which case using a `require` makes more sense that using `onchanges` (which may not be guaranteed to trigger).
19 tasks
jerrykan
added a commit
to jerrykan/postgres-formula
that referenced
this issue
Sep 23, 2021
…ormulas#214) We don't want the `postgres-reload-modules` state reporting any changes to the user unless there is a need to reload the modules. We should only need to reload the modules if the state that manages installing the client libraries makes any changes (ie. new packages installed). In turn, the states created by the `format_state` macro only need to ensure that any module reload occurs before those states are applied. In which case using a `require` makes more sense that using `onchanges` (which may not be guaranteed to trigger).
jerrykan
added a commit
to jerrykan/postgres-formula
that referenced
this issue
Mar 29, 2024
…ormulas#214) We don't want the `postgres-reload-modules` state reporting any changes to the user unless there is a need to reload the modules. We should only need to reload the modules if the state that manages installing the client libraries makes any changes (ie. new packages installed). In turn, the states created by the `format_state` macro only need to ensure that any module reload occurs before those states are applied. In which case using a `require` makes more sense that using `onchanges` (which may not be guaranteed to trigger).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a state does nothing it shouldn't report changes.
The issue caused by #188
The text was updated successfully, but these errors were encountered: