Need help in setting up CICD for Higher Environment

[Vinoth-44]

Expectation: We need to move our customized self hosted api-management-developer-portal from DEV environment to TEST, STAGING and PROD environment.

Description:
We are trying to do automation(CICD) for publishing the self hosted portal content and we are not sure how to handle below scenarios based on environment

Scenario (1):

1. Need to change backend url based on environment

Example,
We have been incorporated our custom back end API in developer portal and this backend API URL will change based on environment.
Dev Backend url: https://appname-rest-api-dev-bcnl-02.azurewebsites.net
Test Backend url: https://appname-rest-api-test-bcnl-02.azurewebsites.net

Scenario (2):

1. Need to change config.design.json, config.publish.json, config.runtime.json settings based on environment

Example,

Dev environment:
managementApiUrl : "https://devApp-management.bcnl.digitalaviationservices.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/xxxxx/providers/Microsoft.ApiManagement/service/devApp"
managementApiAccessToken: "dev access token"
blobStorageContainer: "dev-blob-storage-name",
environment: developemt
backendUrl: "dev back end url"

Test environment:
managementApiUrl : "https://testApp-management.bcnl.digitalaviationservices.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/xxxxx/providers/Microsoft.ApiManagement/service/testApp"
managementApiAccessToken: "testaccess token"
blobStorageContainer: "test-blob-storage-name",
environment: test
backendUrl: "test back end url"

Clarification:

1. Do we need to update anything else apart from these settings ( config.design.json, config.publish.json, config.runtime.json ) ?

2. Please correct if our understanding is wrong on this, Migrate script will only update Administrative content from one service instance to another service instance.

3. Incase If we are not fully depend on administrative, Can we skip the migrate script update ?

[azaslonov]

Hi @Vinoth-44, looks like a question for API Management :) but I can still answer here as well.

1. No, nothing else needs to be updated.
2. That's correct, only raw data/media will be updated. The portal in the destination environment still needs to be published to pick it up.
3. Not sure I understand "not fully depend". Can you please elaborate?

Regarding your scenarios, it will require small changes in the migrate script, like adding more parameters for backend URL, but I don't see any difficulties here. Let me know if you need help with it.

[azaslonov]

Closing due to inactivity.