e the new flavor in the list of available flavors:zenml container-registry flavor list

It is important to draw attention to when and how these base abstractions are coming into play in a ZenML workflow.

The CustomContainerRegistryFlavor class is imported and utilized upon the creation of the custom flavor through the CLI.

The CustomContainerRegistryConfig class is imported when someone tries to register/update a stack component with this custom flavor. Especially, during the registration process of the stack component, the config will be used to validate the values given by the user. As Config object are inherently pydantic objects, you can also add your own custom validators here.

The CustomContainerRegistry only comes into play when the component is ultimately in use.

The design behind this interaction lets us separate the configuration of the flavor from its implementation. This way we can register flavors and components even when the major dependencies behind their implementation are not installed in our local setting (assuming the CustomContainerRegistryFlavor and the CustomContainerRegistryConfig are implemented in a different module/path than the actual CustomContainerRegistry).

PreviousGitHub Container Registry

NextData Validators

Last updated 19 days ago