Depending on AEM version you can use the Assets HTTP API, so no need to recreate your own API. What you'd need to do is create a user on AEM side that is allowed to perform the required CRUD operations in particular DAM path and use these credentials when making the Assets API calls. You should also...

Hi @Sriga311 ,Can you provide some more info to help you more effeciently? E.g. What AEM version are you using? Any SPs installed or other hotfixes?Does this only happen via Jenkins build or is it occurring e.g via Cloud Manager or other build tools?How about the build behaviour in your local dev en...

Depending on the implementation specifics, maybe the Embed core component could do the trick for you. Otherwise I am not sure if any OOTB component capable of doing so.

I think the LCs of XFS should have their respective "local" links adjusted automatically upon rollout. You can try to see the behaviour of these with an AEM Vanilla installation + WKND sample content. Check if you have nested LCs in the target XFs, you might need to adjust the relevant OSGi config: ...

Changing the node name on the fly would be rather costly from an effort perspective (as you need to make sure all references to that page are adjusted, plus managing un/publishing operations too). If the goal is to control the name in the URL, maybe sling:alias (Alias field in page props) would be t...

A bit surprised a Stage environment is not mentioned as an option between Test and Prod (unless you go with Soft-launch approach as mentioned in the article, however you then need to handle existing web properties in a multi-tier setup).

I would need more sample data (i.e. actual paths vs "transformed" paths) to provide a more elaborate answer. It could be the case that asset names have invalid/special chars, so AEM adjusts as necessary to use valid names (and ensuring the CSV is in valid format). By the way, would the asset importe...

For step2, have you tried performing a PUT request to the target path (e.g. /content/dam/myfolder/myasset.png) using the asset as a binary file (using "binary" as body type in postman)?

Can you provide some more information on your clientlibs structure? Are you referencing clientlib paths within the component markup?You can also get a good understanding of how clientlibs work in AEM here: https://experienceleague.adobe.com/docs/experience-manager-65/developing/introduction/clientli...

I understand the hassle, I have encountered similar issues in the past. Back then I used some simple python scripting to quickly adjust the CSV contents to the required values. It should only take a couple of hours and it really pays off in the end, especially considering your large amount of assets...