Select feature
The select bug i wasn't sure what you meant, seems more like a feature than a bug to auto select the first choice. You can always create an empty first choice
hello 🙂 trying out windmill and my
hello 🙂 trying out windmill and my usecase is email automation. I'm following the gmail integration video at https://docs.windmill.dev/docs/integrations/gmail, where the gmail integration shows up as a "OAuth API" in the example video provided, however on my local instance with docker-compose, the gmail integration is in the "Non OAuth" category.
I have added OAuth support for gmail, for instance I can login to my local instance using my gmail with a OAuth 2.0 client I setup on gcloud and configred with "oauth.json" for the docker setup. I'm running the most recent images as of writing this message.
Expanding on that, there is not a single OAuth resource in my local instance, it looks like "image.png" attached.
Am I missing some configuration step or setting? A pointer to docs for this would be awesome, as I seemingly can't find the correct thing to do in order to enable this 🙂...
It pretty much can autoscale and set the
It pretty much can, autoscale and set the workers to only treat a given number of jobs
Is it possible to display only the first
Is it possible to display only the first element of the array? I only need the object schema.
rubenf 7855 I think im really close to
@rubenf I think im really close to getting our production ready self hosted enviornment setup. Quick question about the service account override in the helm chart values override.
CookieMonster 9682 it s not the wrong
@cookiemonster0189 it's not the wrong place. What is your issue ?
postgres with tls
I do this @ravioli
```
import * as wmill from "https://deno.land/x/windmill@v1.100.2/mod.ts";
export async function main(...
How to Use Selenium and Selenoid with Wi...
Thanks. @Felix did that with selenium: https://docs.windmill.dev/blog/use-selenium-with-windmill
Collecting feedback for a new feature
Collecting feedback for a new feature called "Environment" which would have 2 values: Staging and Prod. Essentially, Variables and Resources could be set to have different values based on the environment chosen (which would be set at the run level or workspace level) and users could be barred from having access to prod values. I'm thorn on the subject because there are some overlap with the concept of folders in which you could have "staging" and "production" folders.
I need to update the docs for developing
I need to update the docs for developing locally with imports maps but if you make it work please share!
I think ideally there are 2 independent
I think ideally there are 2 independent behaviors that would work well for this:
- Adding the variable picker in "Test this step"
- persist last "Test this step" on save...
Using docker compose Left for today Will
Using docker compose . Left for today. Will ask on monday if it takes more then 15 min
Named imports
This will be stable but I will likely experiment shortly with import maps such that you could do:
...
import { foo } from "f/foldername/name"
import { foo } from "f/foldername/name"
The way it works is passing your WM
The way it works is passing your WM_TOKEN as DENO_AUTH_TOKENS so that deno itself can fetch the script directly that are served raw
as part of being brex clients and YC we
as part of being brex clients and YC, we got some free billboards advertising on US-101
Alpha Go support
@here We have merged alpha go support and deployed it on app.windmill.dev! Use it it with any imports. Very eager to get feedback from go users!
Gotcha Definitely a cool thing if I
Gotcha. Definitely a cool thing if I could make it available to apple arm
I have the general roadmap of windmill
I have made the general roadmap of windmill public and filled it with starting issues https://github.com/windmill-labs/windmill/issues https://github.com/orgs/windmill-labs/projects/2/views/2