When adding software components to a machine blueprint, assuming no dependencies have been configured for those components, is there a custom property or some other way to mark one of those components as non-blocking in case any of its lifecycle steps fail? Or a way to mark any one of those lifecycle steps (in combination of or exclusive to the entire component as non-blocking) as non-blocking? For example, there could be multiple software components added to a machine blueprint. Some of them are absolutely necessary, while others not so much. I'm looking for a way to mark either an entire component, or a lifecycle stage as "best effort" so if it fails for any reason, the build continues and simply raises a warning.
↧