When deploying a product to test or production stage you'll need to follow some key steps to get it to workaround.
In order to achieve so, please make sure you meet the following.
Built app data is present in S3
The Orchestrator is up to date
Check everything is working out well
You need to make sure all the built application required files are present in the product S3 Bucket, especially the import.json file.
❗Please make sure the URL in import.json is pointing to the app CloudFront either for test or production stage.
If this is the first time you upload the app and have not created the S3 bucket, please follow along Creating S3 bucket
Now is time to add the app to the Orchestrator. To do so please refer to the Adding a new app to the Orchestrator page. Once you're done in there you can continue with the deployment process.
After completing the Orchestrator update, go ahead and create a new git branch called feature/{ yourProductName }, then commit and push the changes. After that, run the script build:prod, verify it creates a dist folder containing the masivapp-root-config.js and masivapp-root-config.js.map files. Now, let’s move to AWS.
Please bear in mind that the S3 you need to modify will depend on which environment you’re applying the changes to.
Test environment
If you need to modify the data in test environment, you’d like to choose the Masiv_platform_labs account and then look for the masiv-ui-public-resources S3 bucket.
Prod environment
If you need to modify the related data in production environment, you’d like to choose the Masiv_platform_Prod account and then look for the masivapp-public-resources S3 bucket.
After identifying the respective S3 Bucket move on and follow these steps:
In the S3 Bucket, go to the /js folder.
Choose orchestrator/ folder.
Delete the current masivapp-root-config.js and masivapp-root-config.js.map files present in the folder. Once the deletion is complete go ahead and click close.
Hit upload. Then drag and drop the masivapp-root-config.js and masivapp-root-config.js.map files contained in the dist folder.
Go ahead and hit upload.
❗Make sure the resource is public by going to Actions > Make public via ACL > Make public
Now let's modify the Orchestrator DynamoDB.