Feature Request - Highlight the policies we have to install when make some changes in an object

[gianogli]

We have an environment with 4 clusters and 2 small business appliances all connected to the same management server.

Each one of these cluster/small business have a dedicated policy but they are sharing the same set of objects.

When we make changes into the objects to implement something in a specific policy of a specific cluster we are not able to know if these changes could impact also other clusters or not. (Now it's not so easy to verify where all the X modified objects are used when you have Y policies with Z rules; with X, Y and Z as large as desired).

What normally happens is that we make some changes in an object used in the cluster A, but we forgot that the same object is used also into the cluster B and C. Se we install the policy on cluster A until some user phone us to tell that something is not working as expected.

Our request is: in a future release, could you add a feature to highlight all the policies that we have to install to implement all the commits made up to that point?

What do you think?

Thanks...

[PhoneBoy · Accepted solution]

You can figure this out easily enough by using "Where Used" on any object you modify.

This will show every policy is used in and where:

Of course, it won't tell you what policy packages are applicable to which gateways.
You might want submit this as an RFE.

[gianogli]

Hi @PhoneBoy ,

yes, I know the "Where Used..." feature but it's not "user friendly" for  this purpose at all.

In this way you tell us that after each commit where we modified X objects we've to check X "Where Used..." windows and write in a sheet of paper the list of policy we've to install. This procedure could be useful when you have 2 policies and you change 3 objects in a commit, but if you have 10+ policies and you change 50 objects in a commit it becomes impracticable.
We will surely open an RFE when we will plan the next EA2GA installation... 😉

Thanks anyway for your support. 8)

[PhoneBoy]

This is something that could theoretically be accomplished by means of a script calling the API.
At a high level, you would:

• Call show-changes between revisions, review the operations output for the added/modified objects
• For each object identified, run where-used

Based on that, you would know what policy layers/package are potentially impacted by the changes.
You could even install-policy for the affected gateways.

[the_rock]

RFE is your best bet.

Andy