You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the documentation states: "When doing wmill script generate-metadata, if a requirements.txt is discovered, the closest one will be used as source-of-truth instead of being discovered from the imports in the script directly to generate the lockfile from the server."
But, when doing wmill flow generate-locks, the lockfiles of inline script always inferred from imports. And I didn't find a way to infer lockfile of inline scripts from requirements.txt.
I think we should make wmill flow generate-locks have the same behavior as wmill script generate-metadata in lockfile inference. Or at least should provide a way to infer lockfile of inline scripts from requirements.txt.
Thanks.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
As the documentation states: "When doing
wmill script generate-metadata
, if a requirements.txt is discovered, the closest one will be used as source-of-truth instead of being discovered from the imports in the script directly to generate the lockfile from the server."But, when doing
wmill flow generate-locks
, the lockfiles of inline script always inferred from imports. And I didn't find a way to infer lockfile of inline scripts from requirements.txt.I think we should make
wmill flow generate-locks
have the same behavior aswmill script generate-metadata
in lockfile inference. Or at least should provide a way to infer lockfile of inline scripts from requirements.txt.Thanks.
The text was updated successfully, but these errors were encountered: