🐛 [source-facebook-marketing] Should not run migration if the legacy field account_id is not present #37367
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: https://github.com/airbytehq/oncall/issues/4131
We have a bug in our migration code where when we attempt to migrate connections that do not have the legacy
account_id
and then crash when we read the config object.This change fixes when we should run the migration by skipping the migration when
account_id
does not exist and therefore nothing needs to be migrated. I'm not 100% sure how this gets triggered because the new fieldaccount_ids
is required, but it could be customers using a side path instead of Airbyte's UI.