3 ms·
Thank you for this: https://github.com/windmill-labs/windmill#cli https://github.com/windmill-labs/windmill#cli My first questions with any new tool of this ki
by mikepurvis 3y ago
Thank you for this: https://github.com/windmill-labs/windmill#cli https://github.com/windmill-labs/windmill#cli
My first questions with any new tool of this kind is immediately:
- Can I run/validate branch versions of the scripts non-destructively, for example as part of pre-merge checks in an IaC CD workflow?
- Can I run my scripts locally without a lot of drama, while developing?
If the answer to either of these questions is no, then the tool is the moral equivalent of directly editing PHP files on the prod machine, unless you're committed to deploying an entire second instance of the tool for staging/dev purposes.
- rubenfiszel 3y agoIn opposite order 2) yes, https://docs.windmill.dev/docs/advanced/local_development https://docs.windmill.dev/docs/advanced/local_development 1) since you can run them locally, you can also run tests as part of your CI. You can also deploy a full windmill as part of your CI, deploy to that local instance, run some e2e tests by calling the webhooks, and then only deploy once those work. Note that we have a full drafting system baked in into the webeditor as well: https://docs.windmill.dev/docs/core_concepts/draft_and_deploy https://docs.windmill.dev/docs/core_concepts/draft_and_deplo... and have support for folders with different permissions and you can create workspaces so you may implement dev/staging/prod in any fashion you like (different folder, workspace, instances)
- gregwebs 3y agoHow would I run unit tests on drafts?
- rubenfiszel 3y agoYou would run your CI in github like you would for normal codebase, the draft aspect is something that is only for the frontend editor. Every time you push from the the CLI (which you could do upon merge to main), it is akin to do a deployment of the new versions.