Blacklist nodes
Blacklist a node in an environment to stop workflows from using it there. Blacklisting is mainly for scripting nodes that can run external programs or shell commands, such as the Python Script, R Snippet, Java Snippet or External Tool node. You can also blacklist other nodes, for example the Python Environment Provider node, so that workflow builders can't create their own Python environments. This works on managed and sovereign environments.
Find the node factory ID
To blacklist a node, you need the ID of its node factory. The ID is the last part of the node's URL on Knime Community Hub.
To find the node factory ID:
- Go to Knime Community Hub, and search for the node you want to blacklist.
- Open the node page.
- Copy the last part of the URL, after the final
/.
For example, the URL of the Python Environment Provider node is:
text
https://hub.knime.com/knime/extensions/org.knime.features.conda/latest/org.knime.pixi.nodes.PythonEnvironmentProviderNodeFactoryThe node factory ID is org.knime.pixi.nodes.PythonEnvironmentProviderNodeFactory.
Blacklist a node in an environment
To blacklist a node:
- Under Global administration, open the Environments page.
- On the tile of the environment, click the three dots and select Edit.
- Under Advanced settings, paste the node factory ID into the entry field, for example
org.knime.pixi.nodes.PythonEnvironmentProviderNodeFactory. To blacklist more than one node, enter each ID on a new line. - Go back to the environment, and click Save changes.
A workflow that contains a blacklisted node can't run in the environment. Typically, the workflow fails to load or execute.