As part of an effort in improving the API Products feature we are considering automatically updating an API Product when any of its underlying APIs are updated.
Currently for example, if there is a change in an API Resources scope, those changes will not be reflected in an API Product that uses those resources unless the API Product is explicitly saved. Due to the fact that API Products are created and managed explicitly by API Publishers and APIs are created solely by API Developers the following scenario needs to be taken into consideration when propagating updates. By default an API Product will be in published state. If an API Developer changes the scope of an API resource that is used by the API Product leading to the API Product being updated then, *1. Who has updated the API Product?* - Technically the API Developer has updated the API Product since the change to the underlying API Resource was initiated by them. But this seems to break the permission model because it allows an API Developer to modify an API Product indirectly. *2. To what gateway environment should the API Product be republished to?* - Determining the gateway environment the API Product is published to is the responsibility of the API Publisher. Currently though the ability to choose this is hidden, it will be available when Life Cycles are supported for API Products. Any updates that occur to an API Product due to an API resource change will not apply till the API Product is republished. But without a API Publishers intervention we are unable to determine which gateway environments to publish to. Publishing to all environments available by default might go against what the API Publisher expects. *Possible solution* Managing API Product updates due to changes in an API resource is a valid requirement. But in order to solve it without crossing the boundaries established for API Developers and API Publishers a new window in the API Publisher UI could be introduced to show API Products that have dependent API updates. This would allow API Publishers to identify API Products that need to be republished and enable them to initiate the process. Please give your feedback on the above. -- Regards, Uvindra Mobile: 777733962
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
