Plan.yml not updating context on save about zaproxy HOT 6 CLOSED

"Open the context" - are you doing this in the ZAP Sites Tree or in the AF Environment?

from zaproxy.

"Run the job in order to get the context held in the yml file to display (this in it's self is very confusing)"
So it sounds like you are editing the Context in the Sites Tree.
This is a missunderstanding :)
The AF plan context can be accessed via the plan Environment.
Updating the Context in the Sites Tree will not update the plan - they are 2 separate things.

from zaproxy.

Ok thats begining to make some sense. I'm actually working my way though through your videos and I've just come accross this bit the editing of the paths directly in the plan.

I think some the of the confusion on my part is that it does take the include and exclude paths from the context pane the first time you create the plan. It also takes the authentication information and puts it in the yml. Loading the automation plan will cause the context editor to appear in the tree ui when run. So the two do appear to be intrinsicly linked.

from zaproxy.

Thats right.
You can create a plan using an existing context, and running a plan created a context.
But updating the context in the Sites Tree does not change the plan.
You can however update the context in the plan.

I can see why this is confusing 😉

from zaproxy.

So I think this is a misundersatanding rather than a bug - ok for us to close this @danbuntu ?

from zaproxy.

Yes very happy to close it. Thank you very much for your help.

from zaproxy.