- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-02-2024 01:16 AM
Hello
We have build a CICD Pipeline to manage Lists in a external Git-Repository. The reason for that is we want to have the option to let our analyst create message templates and config files in a versioned way. Also we don't want that our analyst have to handle the deployment of that files.
Until now the external repo was relativly small and we could use the "/list/save" endpoint. However this repo is rapidly growing and doing for each file an request is overwhleming the application (talking about 120-150 requests per tenant). We could implement a delay, however even without a delay we have the issue that it takes more then 2 hours to update all our tenants.
My Idea was to use the endpoint "/content/bundle" and upload all files as a zip file. Sofar so good, only issue is that we get a error message :
since the endpoint is not documented its a bit hard to guess what the reall issue is.
What i already have seen is that this name "content-bundle...." isn't the name of the tar.gz files i was sending. The original name was
ABC_pre-prod_1719224927.tar.gz. Also the Folder inside the tar file is called like that. To mimic the bundle structure you can download.
Does anybody has done this already?
Greetings.