Hi, so in the case of assets I need to package it right, I was expected to have some actions for that in cloud, that's the confusion was about. How to deploy the package via the pipeline!

Hi, one question though. This method publishes to publish instances only right! What if I need to replicate assets to production from dev! I tried the tree activation for the asset folder, but aint getting deployed to prod.

Hi @kautuk_sahni . The issue was resolved adding additional cofiguration for vimeo support. The custom URL processor remains a mystery!!

Hi @Theo_Pendle That was one thing for sure when I checked now. The other thing was the URL scheme, I changed the scheme from https://vimeo.com/* to https://vimeo.com/.* . I'm quite not sure the significance of this dot.Thanks 

Hi @arunpatidar The vimeo config is,{ "provider_name": "Vimeo", "provider_url": "https://vimeo.com/", "endpoints": [ { "schemes": [ "https://vimeo.com/*", "https://vimeo.com/album/*/video/*", "https://vimeo.com/channels/*/*", "https://vimeo.com...

Yeah got it. I was looking at the wrong pom.Thanks @ArpitVarshney 

 .

Hi @ArpitVarshney This is the pom file, I'm not quite getting what's its mentioned by releaseRepository-URL. <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM...

For the models folder the permission was set to deny for jcr:read and for inside one folder set the permission as allow. But it ain't showing up. The rule is to deny all and allow specific right!

Hi Gaurav. I have the said access privileges, but on trying to access https://console.adobe.io/integrations it's redirecting to https://console.adobe.io/home. What might be the issue?