[MI 4.1.0] Enabling Environment Variable Parameterisation for 'Key' and 'Name' Values in Metadata Files

[SameeraSI]

Deploying the same service to different environments using the APIM catalog[1] poses a challenge as there's no way to customize the ‘key’ and ‘name’ according to the environment. Consequently, in the APIM catalog, identical keys and names lead to the replacement of existing services by new requests, resulting in only one service being visible despite multiple environments. To resolve this, enabling support for parameterising ‘key’ and ‘name’ values using environment variables in metadata files is necessary.

Example:

key: "PurchaseOrders-1.0.0-$env:ENVIRONMENT_NAME"
name : "PurchaseOrders-$env:ENVIRONMENT_NAME"
displayName : "PurchaseOrders"
description: "PurchaseOrders API"
version: "1.0.0"
serviceUrl: "https://{MI_URL}/ep/1.0.0"
definitionType: "OAS3"
securityType: "BASIC"
mutualSSLEnabled: false

[1] https://apim.docs.wso2.com/en/4.1.0/tutorials/integration-tutorials/service-catalog-tutorial/#step-3-configure-the-micro-integrator