Thanks Theo for the link.
I managed to fix this using the below approach.
AliasName1: Test (Without any link to Stage)
AliasName1: Prod (Linked to Prod)
I see when i link it without stage link it is working fine in current environment and when i moved the stage to prod i see the Alias mapped to prod stage is moved along and it got correctly deployed.
------------------------------
Abhijith Parre
------------------------------
Original Message:
Sent: Wed November 27, 2024 06:43 PM
From: Theo Ezell
Subject: Alias management in API Gateway 10.15
Hi Abhijith. Since the same alias is used across stages, you shouldn't assign it to a particular stage. When you promote an API, any dependent aliases are automatically deployed as well as documented here Asset Promotion - IBM webMethods API Gateway
If the alias already exists and you don't want it overwritten, then you should be able to set the Overwrite mode to Custom and deselect Aliases when you promote.
HTH,
Theo
------------------------------
Theo Ezell
Original Message:
Sent: Tue November 26, 2024 08:21 AM
From: Abhijith Parre
Subject: Alias management in API Gateway 10.15
Hi Team
Need some insights on Alias management in API Gateway.
We have created APIs in API Gateway and in Straight through routing configured the URLs as Alias and it worked fine.
Now using promotion management i need to promote to UAT. So we created a stage called UAT and PROD and we see that we can create same Alias name and there is an option to select stage
Alias 1 --> test.example.com --> Stage UAT
Alias 1 --> prod.example.com -->Stage Prod
But when i try to test with this approach i am getting 502 exception and if i remove the stages and just test with Alias it is working fine.
So how do we deploy to production without having to change the Alias again and deploy to different stages.
------------------------------
Abhijith Parre
------------------------------