Include circuit terminations when importing new circuits

[patrickfish]

When adding or editing a circuit, there is no longer a field for Site. Previous to ~1.8.2 you could select the Site that the circuit was associated with.

I do see that I can edit the terminations of the circuit once it's created, but we don't always have a termination point when adding the circuit for the first time.

Is this intended behavior or a bug?

[jeremystretch]

v1.8.0 introduced the concept of circuit terminations, of which each circuit can have up to two. You'll need to first create the desired circuit, and then add terminations (either to a site or to a specific device within that site) separately.

I realize this isn't the most intuitive workflow. It may be workable to combine the creation of a circuit and its first termination in the same form, but I haven't yet looked into it.

[patrickfish]

Ok - that makes sense from what I'm seeing then.

I add circuits as we get the turn-up information from the carrier, which is often before active equipment arrives. It's would be nice to have it tied to a specific site at this point.

Same goes for importing circuits as I see Site is no longer a field there. If I import 100 circuits, they're now somewhat orphaned because I have no other metadata that tells me what site it belongs to. Other circuits don't ever get a termination (ie broadband circuit to a SOHO router) but we still want to have a list of circuits per site.

[jeremystretch]

This is going to be fairly difficult to implement given the current model for circuit terminations, but it's up for grabs if anyone wants to dig into it.

[jeremystretch]

This is almost certainly going to be much easier to accomplish once #4347 has added JSON/YAML-based import for all objects. Marking this as blocked pending that work.