When adding a new system connection via the dashboard... should it be enabled as a connection too?

[ChrisNolan]

It seems like when you add a new system carrier under "Platform -> Carrier Network" in the dashboard (rather than the old school :5002/admin method, it will automatically be enabled as a 'brokerConnection' under the "Connections" tab -- for the first one. But if you add another one, it isn't enabled and you have to manually toggle that one on that screen and not on the Carrier Network screen.

Is this intended behaviour?

Also reference #1100

[ChrisNolan]

Scratch that -- the first one also isn't correctly enabled. The first time you go to the screen it shows it has enabled, but when you try to use it, it isn't enabled. Going back to that route again and it shows it as disabled on that load.

http://localhost:3002/connections/system

[ChrisNolan]

And if you go to it right away, and it shows it is enabled, if you try to disable it and re-enable it again to get around the above you'll get

  File "/home/cnolan/dev/forks/karrio/.venv/karrio/lib/python3.12/site-packages/django/db/models/query.py", line 639, in get
    raise self.model.DoesNotExist(
karrio.server.providers.models.carrier.CarrierConnection.DoesNotExist: CarrierConnection matching query does not exist.
CarrierConnection matching query does not exist.

GraphQL request:3:5
2 |   mutation update_connection($data: UpdateCarrierConnectionMutationInput!) {
3 |     update_carrier_connection(input: $data) {
  |     ^
4 |       errors {
Traceback (most recent call last):
  File "/home/cnolan/dev/forks/karrio/.venv/karrio/lib/python3.12/site-packages/graphql/execution/execute.py", line 523, in execute_field
    result = resolve_fn(source, info, **args)

Not sure what finally 'kicked it' but clicking aorund a bit and it finally showed as 'disabled' which then allowed me to enable it.