fjørdlek
fjørdlek2mo ago

**Workspace Colors** You can now color-code your workspaces to visually distinguish between differe

Workspace Colors You can now color-code your workspaces to visually distinguish between different workspaces, especially when the side-bar is collapsed. This can be particularly useful to differentiate between prod/test workspaces. Changelog: https://www.windmill.dev/changelog/workspace-color Docs: https://www.windmill.dev/docs/core_concepts/workspace_settings#workspace-color
No description
6 Replies
henri-c
henri-c2mo ago
You can watch our weekly lives on our Youtube channel Today's keynote: https://www.youtube.com/watch?v=8tOpodhrg68
Windmill
YouTube
Windmill Weekly #7
00:00 Waiting 03:26 Alex: Ongoing work on Microsoft Teams integration 06:09 Alex: Signing commits with GPG when using git-sync 08:15 Hugo: on_behalf_of for scripts and flows 11:05 Etienne: Integration with Svix for simple webhook creation and management 11:45 Q&A
Pyra
Pyra2mo ago
Support for multiple python runtime versions 🐍 Starting from Windmill 1.449.0 you can select python version you would like to use in your scripts. It is done by putting annotation to the python script. Just add this line on top of your file: #py312 You can also set INSTANCE_PYTHON_VERSION to use specific version globally. Already deployed scripts will always run 3.11 unless redeployed ☝️
Supported versions are: 3.10, 3.11, 3.12 and 3.13
Changelog: https://www.windmill.dev/changelog/select-python-version Docs: https://www.windmill.dev/docs/getting_started/scripts_quickstart/python#select-python-version
rubenf
rubenf3w ago
Release 1.458.0 and current latest TL;DR: Jobs V2 format and migration may take more time than usual if high number of jobs > 1M In release 1.458.0 (not released yet, will be by EOD) we are migrating the format of our jobs in the database (format was 1.5yo) in a non-breaking, back-compatible, no downtime needed way. This format will allow us to improve performance as well as unblock us on some long-awaited features. You can upgrade as usual, but if you have more than 1M jobs, the migration may take around 25mins/Million of jobs. It will not block the cluster and existing workers and jobs will continue to work as usual but new workers and apps will wait for the automatic migration to be fully complete before being able to fully start.
rubenf
rubenf2d ago
We have many changelog to catch-up, starting with a small one. Mocked API file One of our focus this quarter and the next is local development, as part of that, we had the frequent request to be able to have a different behavior when running locally than when deployed. Typically that's done with an env file but that doesn't work in Windmill because you use the api to get variable and resources. Introduced Mocked API for local development: https://www.windmill.dev/changelog/mocked-api-files https://www.windmill.dev/docs/advanced/local_development#mocked-api-files
import * as wmill from "windmill-client@1.450.0-beta.2"

export async function main(x: string) {
await Bun.write("./foo.json", '{}')
process.env["WM_MOCKED_API_FILE"] = "./foo.json"
await wmill.setVariable("foo", "foobar")
await wmill.setResource({ "we": 42}, "foo")
console.log(await wmill.getResource("foo"))
return x
}
import * as wmill from "windmill-client@1.450.0-beta.2"

export async function main(x: string) {
await Bun.write("./foo.json", '{}')
process.env["WM_MOCKED_API_FILE"] = "./foo.json"
await wmill.setVariable("foo", "foobar")
await wmill.setResource({ "we": 42}, "foo")
console.log(await wmill.getResource("foo"))
return x
}
If WM_MOCKED_API_FILE is present, getVariable / getResource will look up first in that object if the value exists. setVariable / setResource will set it there. If the environment variable is set but no file exists, it is set to an empty mocked API.
Mocked API files
Windmill now supports simulating API interactions locally with a mocked API file.
Local development | Windmill
Windmill has its own integrated development environment, but you can also develop and run scripts locally, both with self-hosted and cloud instances.
fjørdlek
fjørdlekOP2d ago
Microsoft Teams - Workspace Scripts and Handlers (EE) Following the integration of Microsoft Teams for critical alerts, Windmill now supports triggering scripts directly from Microsoft Teams using workspace scripts as well as error, success, and recovery handlers for both workspaces and schedules https://www.windmill.dev/videos/teams_handler.mp4
Microsoft Teams integration | Windmill
Microsoft Teams is a collaboration platform that integrates with Office 365.
wendrul
wendrul19h ago
Oracle Database support In addition to the other supported databases and sql languages, you can now add and interact with Oracle Database instances from Windmill ! See the docs: https://www.windmill.dev/docs/getting_started/scripts_quickstart/sql#oracle
Oracle support
Windmill now supports Oracle scripts.
Quickstart PostgreSQL, MySQL, MS SQL, BigQuery, Snowflake | Windmill
In this quick start guide, we will write our first script in SQL. We will see how to connect a Windmill instance to an external SQL service and then send queries to the database using Windmill Scripts.

Did you find this page helpful?