Hi Martin, Creating another cartridge type is just changing the type parameter of the existing cartridge json if you are using the base image approach and deploying the new json.
If the requirement is only the easiness in testing, I don't think implementing this feasibility is necessary given that we are in a tight schedule. However if there is a real world use case I am OK. Touched, not typed. Erroneous words are a feature, not a typo.
