If we set "require-adobe-auth" to false in the ext.config.yaml the worker runs successfully. So it seems like, that AEM can't authenticate against App Builder.
Hi together,HI @Dmytro_Panchenk @yeedg , we have the same issue.Our App Builder Project and the AEM is in the same Org. How exactly did you @Dmytro_Panchenk update the Asset Compute "Adobe IMS Technical Account Configuration"? I can't edit the default configuration. I can create a new "Adobe IMS Tec...
Helpful - yes! But unfortunately nothing that works for us that doesn't include writing custom implementations. I would expect, that AEM can do this out of the box - especially because there are multiple ways which should work, but don't respect the "include children" options for Tags.
Hi @aanchal-sikka ,thanks for your Answer! Unfortunately Option 1 and 2 don't work for us (see the other answers). Option 3 does not work, because we I didn't find a way to replicate a whole tree inside the Cloud Environments (it only works for single Nodes)
Thanks for your answer! Unfortunately, we can't use this approach, because we have some additional logic which hooks into the publish event, which we don't have if we publish the whole package at once.
Hi @lukasz-m ,unfortunately, this doesn't work. The workflow ignores the children (even tough the parameter "-includeChildren=true". The workflow only publishes the selected root tag.Do you know a workaround for this?Thanks!
Is there a way to publish a whole tree of tags at once?We have multiple tag trees containing a few thousand tags in AEMaaCS. How can we publish all of them at once? I already tried it with "manage publication" while publishing a page, but this doesn't work, because process doesn't include children (...