-
Steps to reproduce
1. Create new virtual env and activate
2. Install a local `pollination-dsl` dependency
3. Run `pollination dsl translate `
Expect:
Command fails with:
```console
urllib.…
-
After going back and forth on how to name the plugins and recipes it looks like the cleanest way to do it is to enforce namespace packaging for all the packages. With this approach all the packages wi…
-
The current iteration of this recipe generates duplicated task output names. This shouldn't be possible in theory so we should add some more validation on Queenbee's end to make sure it doesn't happen…
-
This is useful to make the library compatible with queenbee-pollination for deploying the recipes.
-
As much as the integration looked fancy and appealing at the start it is becoming really hard to catch all the possible cases. There are some inherent issues with the idea. For example, to be able to …
-
The most recent fix https://github.com/pollination/queenbee/commit/41fb857c2f2658f390e0eab5a787616266d91791 breaks the C# SDK generation. List is not recognized inside Union (AnyOf) during the transl…
-
We should use this repositories as the single source for both ladybug tools and pollination recipes. We need to copy the workflow from the private garden repository here.
-
We need to add a sample folder here and run the recipes against the folder before pushing them to Pollination and updating them locally. This will ensure that we don't break the recipes for the users.
-
The local recipe object doesn't have owner key.
Do we want to use maintainer's info for displaying owner on UI?
cc @mostaphaRoudsari
-
It will be helpful when packaging recipes and operators in other contexts than a user's machine to be able to generate a tarfile bytes/file object without writing any data to files.
This is pretty …