Leo Kirchner
Leo Kirchner
In addition, this should auto-populate from `nautobot_ssot.contrib.NautobotAdapter`
Yeah terraform with the plan feature is something that mirrors this very well
This may be particularly interesting for 'outgoing' jobs, i.e. ones where we mutate the state of an external system (think a network device controller) using data from Nautobot.
As `validated_save()` today already runs validations from the data validation engine, is the ask here to move that validation from the object CRUD into the loading? I.e. somehow calling `full_clean()`...
Alright, so purely a documentation issue then, no code required on the SSoT side?
Very simple possibility would be: On `PolicyRule.validate`, check whether another `PolicyRule` with the exact same, directly firewalling-related fields (i.e. source/destination/protocol/etc., not `request_id` or similar) already exists within the same `Policy`...
What would you think about this being another category for `AddressObject` objects besides range, FQDN, etc.?
A little bit of both. Currently I can only retrieve policies assigned _directly_ to devices, not those assigned through dynamic groups. I talked about this with the Nautobot core team...
I understand the sentiment, but taking away the thoughts about the implementation and just thinking of the actual feature for now, don't you think it would be useful to have...