Issue with the new blue-green strategy

[rage28]

Description

When using the new blue-green strategy with deploy the process goes as follows:

1. Rename any existing application and suffix "-live" to the app-name
2. Create new application with of the newer version to be deployed with name "-idle"
3. Bind services to the app
4. Upload application/module "-idle"
5. Stage and start the application
6. If application starts successfully, then rename the application and remove the "-idle" suffix
7. Stop and remove old "-live" suffixed app
8. Cleanup

We are facing 2 issues with this approach:

• When the application "-idle" is renamed and this prefix is removed, this new name does not flow down to Kibana (and probably many other bound services which depend on the application name). In kibana we still see the application name with the "-idle" prefix
• If we use the "Cross-MTA Dependencies" feature we face the following error:

17:12:49 Could not update application "my-app-idle" from MTA "my-app-mta-id" for subscription "shared-subscription": 404 Not Found: Application my-app-idle not found.

Your environment

• MultiApps CF CLI Plugin version - 2.7.0
• which CF vendor is used - SAP CP CF

[IvanBorislavovDimitrov]

Hello,

Regarding the first issue - the deploy-service just renames the application from "app-idle" to "app". It uses the Cloud Controller in order to do that. Do you experience this issue if you use "cf rename" command?

Second issue:

1. Could you attach the MTA operation logs? The command is printed at end of the deployment: "cf dmol -i <operation_id>". You can find the operation ids via "cf mta-ops --all".
2. Do you deploy these MTA applications simultaneously the "provider" and the "consumer" of the Cross MTA dependency?

Best regards,
Ivan