...
WSO2 Governance Registry 4.6.0 allows only one lifecycle to attach to a particular governance artifact type. However, when an artifact governed in the G-Reg and is in the Store front, it gets associated with a Store-specific life cycle in the Store, and also have another development life cycle within G-Reg itself. Therefore, the functionality of the resources has to be is independent of the life cycles. With the new improvements in G-Reg 5.0.0 onwards, you can associate multiple life cycles to a resource. All associated life cycles can perform operations independently. .
For an example, when you add a new service in the Management Console, it is associated with a Service-specific lifecycle by default. You view it in the Attached Life-Cycles panel as shown below.
You can associate another life cycles to the resource by adding the life cycle in the Lifecycle panel, when you add the resource as shown below.
Now, you view the EndPointLifeCycle you selected above also associated to the Service artifact in the Attached Life-Cycles panel as shown below.
| Tip |
|---|
This does not limit the service provider to associate other available life cycles. All associated life cycles |
...
can perform operations independently. You can view and edit the details of each life cycle by selecting them from the drop down menu in the Attached Life-Cycles panel. Deleting a lifecycle from a resource does not alter other associated life cycles or their states. |
For an example, when If you add a new service in the Management Console, it is associated with a Service -specific lifecycle by default. If you add the service using the publisher frontPublisher, then the service it gets associated with a Service-specific life cycle and a Store lifecycle by default.