✨ Source Facebook Marketing: update API to v21.0

[h0rban]

What

According to documentation, the Marketing API version currently used by the connector is being deprecated on 2025-02-04

Issues:

• #50850

How

Updates the facebook-business package version to 21.0.5

Review guide

1. airbyte-integrations/connectors/source-facebook-marketing/pyproject.toml
2. airbyte-integrations/connectors/source-facebook-marketing/poetry.lock

User Impact

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

[vercel]

@h0rban is attempting to deploy a commit to the Airbyte Growth Team on Vercel.

A member of the Team first needs to authorize it.

[marcosmarxm]

Thanks for the contribution @h0rban I asked the connector team to take a look. They will probably read all the changelog and check if there any other updates are necessary to change the version. As the deprecation will only happen in February we have couple of weeks.

[marcosmarxm]

There are some internal testing happening to accept the change. Depending it can impact in some breaking changes and the team will open a different pull request to get it merged @h0rban. One example was the migration from v17 to v19 where Facebook changed the token length.

[maxi297]

Hey @h0rban, thanks for your contribution! We have two concerns that prevents us from testing:

• The poetry lock is outdate: We have error "Error: poetry.lock is not consistent with pyproject.toml. Run poetry lock [--no-update] to fix it." has you can see on https://storage.cloud.google.com/airbyte-ci-reports-multi/airbyte-ci/connectors/test/pull_request/h0rban_update-to-api-version-21/1736950152/5950db80842395cad37684c7b1a4b188b838e9bf/source-facebook-marketing/3.3.24/output.html
• Branch is outdated: The branch should be up-to-date with master to prevent conflicts.

Let us know once it is updated and we will do the testing part for you. Thanks!

[h0rban]

@maxi297 ^

[marcosmarxm]

@maxi297 i triggered tests let's wait for the results

[marcosmarxm]

@maxi297 regression tests failed (not sure how impact it has) and a spec test is also failing...

[maxi297]

Small update on this:

• We have figured our the spec issue. It's because we rely on the lib to provide fields for custom insights reports. With the lib version update, the values have changed. That being said, it is only adding valid so this change is be backward compatible. We just need to add disable_for_version in the acceptance-test-config.yml
• For regression testing, we will run a couple on our side to valide a few more things. We'll keep you posted