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
If you move a script from under a user to a new folder that you create inline, then deploy that script to another workspace which has Git Sync enabled, the new folder will be missing its metadata file. If you then do a wmill push with the source from Git Sync to a separate Windmill instance, the folder won't show up in that instance's folder list.
To reproduce
Ensure there are at least two workspaces in your Windmill instance, let's call them A and B.
A should be able to deploy to B.
B should have Git Sync turned on.
Create a new script under your user in workspace A and deploy it there.
Deploy the script to workspace B.
In workspace A, move the script from under your user to a new folder.
From workspace A, deploy the script to workspace B.
In the Git repository for workspace B, observe that there is no folder.meta.yaml in the new folder.
From the Git repository for workspace B, push to a separate Windmill instance.
In the separate Windmill instance, observe that the new folder does not show up in Folders & Groups > Folders, but the script itself does show up in Home.
Expected behavior
After deploying to workspace B, the new folder's folder.metadata.yaml should get created, and when pushing the source to a separate Windmill instance, the new folder should show up in the Folders list.
Screenshots
No response
Browser information
No response
Application version
v1.334.0
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
If you move a script from under a user to a new folder that you create inline, then deploy that script to another workspace which has Git Sync enabled, the new folder will be missing its metadata file. If you then do a
wmill push
with the source from Git Sync to a separate Windmill instance, the folder won't show up in that instance's folder list.To reproduce
Expected behavior
After deploying to workspace B, the new folder's folder.metadata.yaml should get created, and when pushing the source to a separate Windmill instance, the new folder should show up in the Folders list.
Screenshots
No response
Browser information
No response
Application version
v1.334.0
Additional Context
No response
The text was updated successfully, but these errors were encountered: