-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
2017.7: module.wait used as in documentation provides deprecation warning #47033
Comments
i'm not seeing that warning when i run this state:
But when i change the state to module.run i then see the warning:
Are you only running that state? Is there possibly another module.run state in there? Any other ideas on how to replicate this issue? |
I failed to grep I managed to reproduce with this:
|
Ping @Ch3LL |
thanks for the test case I am able to replicate this now. It seems to be caused by the combination of contents and the watch_in. ping @saltstack/team-core any ideas here? |
Probably because module.wait only runs on a watch_in, and module.mod_watch is aliased to whatever module.run you are using, and if you don't move to the new module.run format (use_superseded), then the old module.run is used on a watch/listen. https://github.com/saltstack/salt/blob/2017.7/salt/states/module.py#L554 Which is what that deprecation message is about. |
Yes, adding
avoids this warning. |
@Talkless you okay to close this now? |
I am not sure, looks like a workaround. What will happen in Sodium if one does not add that option? |
The old format goes away starting in sodium, and it will move to the new
format.
…On Sun, Jul 29, 2018 at 5:30 AM Vincas Dargis ***@***.***> wrote:
I am not sure, looks like a workaround. What will happen in Sodium if one
does not add that option?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#47033 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAssobs5Uq87opNzRW_rApn7AUgdPhiHks5uLY7TgaJpZM4TR2jK>
.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Description of Issue/Question
running
module.wait
with2017.7.5
produces warningThe function "module.run" is using its deprecated version and will expire in version "Sodium".
:I know that
module.run
has new way of specifying modules to be executed, but there is no instructions on howmodule.wait
should use new declaration style. Using it as before produces mentioned deprecation warning.Setup
My minion-restarting state (changing minion conf invokes this)
Steps to Reproduce Issue
Make
module.wait
to run, logs are above.Versions Report
The text was updated successfully, but these errors were encountered: