Clustering & partitioning customization is not being propagated to the customer after installing a carol app
Description
PRDE - Bug default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
@Douglas Coimbra Lopes
02 - PROBLEM (WHAT'S THE ISSUE?):
- Clustering & partitioning customization is not being propagated to the customer after installing a carol app. The platform is keeping the default clustering & partitioning on the customer tenants with the app installed.
- It happens for the first and also the Update version of the carol app.
- Dev Tenant App Clust & part:
- DM snapshot is attached to the card for further tests
Customer tenant after installing the version of the app
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
- Scenario1: First app version
- Access or Create a new Data Model
- Customize the clustering & partitioning
- Create a new app
- Release the app version
- Approve the app
- Install the app on the customer or unified tenant
- Check the clustering & partitioning for the data model with the default setting.
- Scenario2: Update app version
- Access or Create a new Data Model
- Keep the default clustering & partitioning
- Create a new app
- Release the app version
- Approve the app
- Install the app on the customer or unified tenant
- From the dev tenant, customize the clustering & partitioning for the data model
- Create a new app version
- Release the app version
- Install the updated version of the app on the customer or unified tenant
- Check the clustering & partitioning for the data model was updated
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT):
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):