WSO2 redeployment should not be triggered if nothing changed in the API definition (OpenAPI document, API configuration/properties, etc).
This would:
Save deployment time as if there is nothing to change the custom resource will not run longer than it needs.
Make deployments safer as even small changes can cause WSO2 to be out of sync across its instances (i.e. when changing the properties attribute)
Proposal
Have some sort of "state" to be checked before trying to update an API.
Example: a checksum of the OpenAPI document, etc. of a previously succeeded deployment. If still the same, then there is nothing to do.
Problem being solved
WSO2 redeployment should not be triggered if nothing changed in the API definition (OpenAPI document, API configuration/properties, etc).
This would:
propertiesattribute)Proposal
Have some sort of "state" to be checked before trying to update an API. Example: a checksum of the OpenAPI document, etc. of a previously succeeded deployment. If still the same, then there is nothing to do.