topic Re: API install-policy behavior if policy name changes in API / CLI Discussion

API install-policy behavior if policy name changes

Andreas_Lorenze — Thu, 24 Jan 2019 11:52:31 GMT

Hi,

how does "install-policy" behave when the policy name to be installed does not match to the one already installed on the target gateway. Doing it by GUI you get a warning, but you can force it. The API reference error codes didn't gave me a hint.

1. Will the install fail? If yes, any option to force it?

vice versa

2. If it would just install, any option to force to stop with error?

thx in advance

Re: API install-policy behavior if policy name changes

PhoneBoy — Sat, 26 Jan 2019 20:10:34 GMT

As this is an API question, I am moving this to Developers (Code Hub)‌

And, you appear to be correct, the install-policy API call does not let you know that you are changing the policy from X to Y.

I'm also not clear what API call you need to make to check this beforehand.

Amiad Stern‌?

Re: API install-policy behavior if policy name changes

Amiad_Stern — Sun, 27 Jan 2019 07:38:11 GMT

This is a bad behavior of install policy via API. We will address it in the next versions. Thanks for your input.

In the mean time, this logic can be accomplished with few api commands (as a "script"):

1. get relevant policy installed on target (show gateways-and-servers)

2. check if the policy installed is different from the one that is about to be installed

3. fail if it is different (or make your script interactive and wait for user input to keep installation)

Re: API install-policy behavior if policy name changes

Andreas_Lorenze — Mon, 28 Jan 2019 11:15:15 GMT

Hi Amiad,

thx for making it clear.

Just the workaround is not really one. You need to switch to detailed-level full for the show command. And to work through that is quite complicate as the output does not only contain gateways with "access-policy". So it bit much effort just to cover that.

Re: API install-policy behavior if policy name changes

Amiad_Stern — Mon, 28 Jan 2019 18:56:24 GMT

You're right there is some extra work to do, but you can use jq to filter only relevant results which might make it easier.