Jiří Suchomel
Jiří Suchomel
When new codeset is registered, it's automatically marked as "current". That seems nice because it's not necessary to provide codeset for further actions. However it is also confusing, because e.g....
When fuseml is creating a namespace while installing an extension, it labels it so to mark itself as the creator of such namespace. Later, if such labeled namespace is detected,...
quoting @stefannica from https://github.com/fuseml/fuseml/pull/263 _I also have a suggestion for how to implement the delete operation: create an individual role for every extension that needs permissions, and have all those...
Downloading latest client is especially not useful when running the installer from the container
When invalid identifier is given to delete command, delete operation does not fail (which _might be correct_), however the CLI reports e.g. _Codeset %s successfully deleted_ (same for workflows and...
Part of https://github.com/fuseml/fuseml/issues/224 Necessary additions to the installer: https://github.com/fuseml/fuseml/pull/236 https://github.com/fuseml/fuseml/pull/241 Installation instructions for the extension: https://github.com/fuseml/extensions/pull/31
I uninstalled my setup (using fuseml-installer uninstall) and tried to install version 0.2 with `fuseml-installer install`. This has failed with ``` 🚢 Deploying Tekton.........error installing FuseML: installing tekton/install/profile-all.yaml failed: Error...
They could be required by some other extension. So either we can't remove them, or we must make sure they are not required by anything that is currently installed.
Currently server creates "fuseml user" every time when creating project - and name of such user is devised from the project name, password is hard coded. This user is used...
FuseML recipe templates (or actions) are the main concept FuseML is based on. Currently, a FuseML action is expressed as a Tekton pipeline, but as we add more and more...