wmill sync pull to get the code out of my workspace, into a local folder and pushing to my git repo. Today I wanted to get more productive by learning how to use the VScode plugin. Got that setup, been working with it all day, its great. Just tried to do a wmill sync push and now the cli thinks it needs to rename all the scripts on the server? Note, the problem appears to be tied to the defaultTs option in the wmill.yaml file. I kept having to click to switch to deno from bun so I changed that to option in the yaml. If I change it back to bun and then try to do the push again, the sync does not think it needs to do a bunch of renaming. What do I need to do here? I definitely want my default to be deno and all my .ts files are already named .deno.ts, so I don't know why the cli thinks they need renamed on the server?
@everyone Windmill is the fastest workflow engine but many times the comparison with other workflow engines was stuck on low-code vs full code flows. I'm proud to release the ALPHA of: **Workflow-as-Code v2 — Write workflows as plain code** We completely rebuilt Workflow-as-Code from the ground up. Instead of a visual flow builder, you write your entire workflow as a regular TypeScript or Python script — with all the reliability of Windmill's execution engine behind it. ``` import { task, step, sleep, waitForApproval, workflow } from "windmill-client"; const process = task(async (x: string) => `processed: ${x}`); export const main = workflow(async (x: string) => { const a = await process(x); const urls = await step("get_urls", () => getResumeUrls()); await sleep(60); await waitForApproval({ timeout: 3600 }); return { processed: a }; }); ``` Each task() call runs as a separate checkpointed job — if your workflow fails halfway through, completed steps are skipped on retry. step() checkpoints inline code without spawning a child job. sleep() and waitForApproval() suspend server-side without holding a worker. What's new: - Direct function calls — no more string-based step references or passing context objects. Just wrap your functions with task() and call them normally - Module support — split your workflow across multiple files with taskScript("./helper.ts"), each module gets its own editor tab - Parallel execution — Promise.all() / asyncio.gather() just works - Full primitive set — task, taskScript, step, sleep, waitForApproval, getResumeUrls - Python & TypeScript — both languages supported with idiomatic APIs (@task() decorator in Python) - Live timeline — real-time visualization of step execution, durations, and status in the UI Available now in v1.652+. https://www.windmill.dev/docs/core_concepts/workflows_as_code
rubenf · 5d ago
We're live here https://discord.com/channels/930051556043276338/1278977038430240813
henri-c · 3w ago
Infrastructure as code
rubenf · 2mo ago