I discovered the root cause of the issue. The jackrabbit documentation is actually correct: it only requires the "replace" mode on the parent filter.xml entry, and then the actual child nodes need to be absent in the package - this will remove them.But there were two issues preventing this:1.An obso...

Thanks Karishma, but trial-and-error is not something I was looking for. Your second suggestion contradicts the Jackrabbit documentation in two ways: "merge" mode by definition does never modify existing contentan exclude pattern makes the package manager skip this node upon installation (regardles...

 I have a package that install the etc map entries on my Publishers.I currently have some mapping configs there that are obsolete, but must be removed because they break the new correct mapping.all my mappings are located underneath /etc/map.exampleThe rule in the filter.xml is<filter root="/etc/map...

Yes thanks, I already know this is the type and not the name. But having multiple "dev" type environments (we have 4) makes it confusing for users, because they always have to remember the environment ID in the URL, and its easy to get mixed up and change something in the wrong browser window.So in...

We have multiple development environments in AEM cloud. In the UI, they all show "dev" in the green icon at the top left.This can be easily confusing. How can this be changed to match the name of the environment, e.g. "qa" or whatever we use as a custom environment name?  

The solution is to just set the global LogLevel to warn in the custom vars, since debugging with a more detailed log level is not possible anyway in the cloud.

Actually this does not work, the Adobe cloud pipeline fails2025/10/14 12:11:35 Apache configuration uses non-allowlisted directives: conf.d/variables/custom.vars:43: LogLevel conf.d/variables/custom.vars:43: LogLevel conf.d/rewrites/lfg_rewrite.rules:26: LogLevel

Thanks, sounds reasonable.I tried to apply this.There is a default LogLevel directive in dispatcher_vhost.conf but that is an immutable file.Multiple LogLevel directives are fine for Apache, so I added it in one of the custom vhost configsNow the managed_rewrite_maps:debugerrors are gone from dispat...

In my dispatcher_httpderror log, I keep getting the following messages. Fri Oct 10 23:59:24.646793 2025 [managed_rewrite_maps:debug] [pid 123] [cm-p123-e123-aem-publish-123] Managed rewrite maps check in progressFri Oct 10 23:59:24.650947 2025 [managed_rewrite_maps:debug] [pid123] [cm-p123-e123-aem-...

Hi Arun, unfortunately your answer is wrong. It's possible to put the actual files into the "enabled" Folder directly. The pipeline log prints a warning, but continues and it works.