✨ Source Facebook Marketing: Include socat binary in docker image

[git-phu]

What

• Similar to ✨ Source Shopify: Include socat binary in docker image #30560

This is for

• https://github.com/airbytehq/airbyte-internal-issues/issues/5298
• https://github.com/airbytehq/airbyte-platform-internal/pull/8870

How

Build and publish source Facebook Marketing to include socat in the docker image.
This will then be used in https://github.com/airbytehq/airbyte-platform-internal/pull/8870

🚨 User Impact 🚨

None from this PR alone (socat will be added to the image but won't be used until https://github.com/airbytehq/airbyte-platform-internal/pull/8870 is merged.)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 22, 2023 10:59pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[gosusnp]

LGTM but I'd rather make sure someone from connectors take a look.
Looking at the dockerfile, shouldn't we have a base image for python cdk based connectors instead of rebuilding everything from scratch?

[git-phu]

Looking at the dockerfile, shouldn't we have a base image for python cdk based connectors instead of rebuilding everything from scratch?

@gosusnp yes, connector ops is actually in the middle of recreating the bases too, so for general rollout we'll need to add it there. This is just for testing on specific existing connector Dockerfiles

[erohmensing]

[airbyte-oss-build-runner]

source-facebook-marketing test report (commit aa32310b16) - ✅

⏲️ Total pipeline duration: 102mn27s

Step	Result
Connector package install	✅
Build source-facebook-marketing docker image for platform linux/x86_64	✅
Unit tests	✅
Integration tests	✅
Acceptance tests	✅
Code format checks	✅
Validate airbyte-integrations/connectors/source-facebook-marketing/metadata.yaml	✅
Connector version semver check	✅
Connector version increment check	✅
QA checks	✅

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-facebook-marketing test