THE ONE PLACE that decides whether a connection reads and writes the shared integration catalog
or its own.
Deliberately one place. A flag consulted in several is a flag that will eventually disagree with
itself, and here the two answers are not merely different — a shared write during a
per-connection run puts one tenant's discovery into every other tenant's catalog and reports
success.
Two levers, in precedence order:
CompanyIntegration.Configuration.catalogSource — per connection. This is the primary
control, and it is per-connection rather than per-process for two reasons: it survives a
deploy (an environment variable set on the box does not — a deploy rewrites the env file),
and it lets one process run some connections each way at once, which is what makes cutting
over one connector at a time possible.
MJ_INTEGRATION_CATALOG_SOURCE — a global override, and the reason it exists is rollback:
it is the only lever that does not require reaching a connection's Configuration through a
workspace that may be the thing that is broken. Keep it after the fleet cuts over.
Default is 'Shared'. The tables can therefore exist, be backfilled and be verified against live
traffic before anything reads or writes them.
THE ONE PLACE that decides whether a connection reads and writes the shared integration catalog or its own.
Deliberately one place. A flag consulted in several is a flag that will eventually disagree with itself, and here the two answers are not merely different — a shared write during a per-connection run puts one tenant's discovery into every other tenant's catalog and reports success.
Two levers, in precedence order:
CompanyIntegration.Configuration.catalogSource— per connection. This is the primary control, and it is per-connection rather than per-process for two reasons: it survives a deploy (an environment variable set on the box does not — a deploy rewrites the env file), and it lets one process run some connections each way at once, which is what makes cutting over one connector at a time possible.MJ_INTEGRATION_CATALOG_SOURCE— a global override, and the reason it exists is rollback: it is the only lever that does not require reaching a connection's Configuration through a workspace that may be the thing that is broken. Keep it after the fleet cuts over.Default is 'Shared'. The tables can therefore exist, be backfilled and be verified against live traffic before anything reads or writes them.