Why are the rollout-plan entries in the domain.xml and also the directory that houses the rollout plan in data/content hashed in JBoss EAP?

Solution Verified - Updated -

Issue

It is not clear why to hashing the values and rollout-plans would be much easier to manage if they were directly in the domain.xml as un-hashed entries. There is no guarantee that all hosts in a domain are running when a rollout-plan is created, so how would these directories get synced otherwise? It's not even like the hashed value is consistent after the first rollout-plan is created. Every time a new rollout-plan is added, this hashed value changes.

    <management-client-content>
        <rollout-plans sha1="db0730562f4221a7b6bdb2d049a2f0d108c79d55"/>
    </management-client-content>

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 7.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content