Non-Functional Features Question

[IanGraham]

Hoping someone from the development team can answer a few rapid fire questions. I have search around and maybe I am not finding the answers but there are several "buttons" in Expedition that seem like they were put there for a reason but maybe aren't yet functional:

• Modifying the XML API Push has options for different operations (Set,Edit,Rename). In my limited testing nothing but Edit seems to work. Is this the case or am I doing something wrong? Does expedition some how track object renaming so that, for example, if I imported a PAN-OS config for machine learning, and then renamed an existing object, that API call would be a rename or match the previous objects for update when we push?
• What does the "clean" option do in the API export?
• What is the status of the real-time config update? Last I heard it was not yet ready. Is any part of it functional today?

Thanks to everyone on the expedition team who I am sure are putting most of the effort into 2.0 at the moment. We use this tool all the time and it is indispensable.

[abarbany]

Hi @IanGraham 

By default we are creating the export API calls as EDIT. If you want to use another method like SET or RENAME then I would suggest you check your Panos device API. Since the structure of the body may need to change to be able to use a different method.

About the renaming of objects we do not take into consideration. What we will do is create an API call that will create this new object with the new name.

The CLEAN option is to create API calls that removes objects in case you want to remove any. In Expedition2 we have added another functionality so when you create subatomic API calls if you had remove an object in the tool it will appear a DELETE api call automatically.

About the real-time config update status I need to check internally, I will get back to you with more information