...
WSO2 Governance Registry 4.6.0 allows only one lifecycle to attach to a particular resource (e.g. a service) governance artifact type. However, when an artifact governed in the G-Reg and is in a store front, the artifact within G-Reg itself needs to have a development life cycle and in enterprise store, it needs to be the Store front, it gets associated with a store Store-specific life -cycle).
If you want
There can be situations where a resource might need to get associated with two or more life-cycles (e.g. The framework that we need to support should cycle in the Store, and also have another development life cycle within G-Reg itself. Therefore, the functionality of the resources has to be independent of the life - cycles.
With this the new improvement improvements in G-Reg 5.0.0 onwards we allow resources to be associated with multiple lifecycles. All associated lifecycle , you can associate multiple life cycles to a resource. All associated life cycles can perform operations independently. In case of a service
This does not limit the service provider to associate other available life cycles. Furthermore, deleting a lifecycle from a resource does not alter other associated life cycles or their states.
For an example, when you add a new service in admin console, it’ll be by default associated with a service specific lifecycle, whereas if the Management Console, it is associated with a Service-specific lifecycle by default. If you add the service in enterprise using the publisher front, then the service will be gets associated with a Service-specific lifecycle life cycle and a store lifecycle. This doesn’t limit the service provider to associate other available lifecycles. Furthermore, deleting a lifecycle from a resource doesn’t alter other associated lifecycle or it state.Store lifecycle by default.