Customization Archive Deployment Process Simplification

Hi Team,

Customization Archive process should be simpler than the current process. Customization Archive deployment supports HTTP/HTTPS/FTP/FTPS process, and it supports WGET only.

It is not necessary that every customer will be having FTP or HTTP infra.

Since MAS/Manage can be deployed on multiple cloud platforms or On-Prem, there will be different kind of challenges.

In AWS, with S3 if it is public link, then anyone can download the archive. (Major Security Concern)

If S3 file link is private, then it is complex to set this up in MAS/OpenShift.

In Azure, with Azure file storage if it is public, then same security concern. If it is private, then MAS will not support.

When you enable SAS token URL in azure, then this will have multiple special characters and also this will be accessible for limited time. Still MAS does not support that SAS token URL. WGET also doesn't work with this URL. You must put the URL in double quotes in order to download the same. but again MAS does not support double quotes.

So impossible to configure archive with Azure.

So, looking for a way to simplify this customization archive deployment process.

May be, there should be a UPLOAD/DOWNLOAD option instead of URL setup. or IBM can come up with something else to simplify this process.

Or there should be a way to deploy customization archive securely in Azure also.

Thanks for the understanding.