[2.2] Job-based CSV import should optionally be atomic

[glennmatthews]

As ...

Nelly - Network Engineer

I want ...

To have the option for CSV import (via system Job) to be either non-atomic (each individual CSV row succeeds or fails in creating an object on its own) or atomic (the entire CSV file creates objects successfully or else no objects are created at all).

Atomic import was the only option in 2.1 and earlier, but may or may not be the desirable default in 2.2.

So that ...

If I have a large data file that may contain errors on some rows, I have the option to repeatedly retry it, cleaning up errors as I go, until the entire file is successfully importable.

I know this is done when...

I have an option when submitting the Import Objects job to choose how I want errors to be handled.

Optional - Feature groups this request pertains to.

• Automation
• Circuits
• DCIM
• IPAM
• Misc (including Data Sources)
• Organization
• Plugins (and other Extensibility)
• Security (Secrets, etc)
• Image Management
• UI/UX
• Documentation
• Other (not directly a platform feature)

Database Changes

None

External Dependencies

None