chore(ingestion-base): bump base image packages

[david-leifker]

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Summary by CodeRabbit

• New Features

  • Introduced new packages for Azure cloud services to enhance integration capabilities.

• Improvements

  • Upgraded several key Python packages to improve performance, security, and compatibility.
  • Enhanced support for OpenTelemetry through updated libraries.
  • Improved configurability of Docker Compose files through environment variable usage for service images.

• Bug Fixes

  • Various dependencies were updated to resolve known issues and improve overall system stability.

[coderabbitai]

Walkthrough

The recent updates enhance the project's Docker configurations and Python package dependencies. Key changes include version upgrades for essential libraries in base-requirements.txt, the addition of Azure-related packages, and the implementation of dynamic image versioning in Docker Compose files. These adjustments prioritize security, performance, and maintainability, ensuring the application remains robust and adaptable to changes in the environment.

Changes

Files	Change Summary
docker/datahub-ingestion-base/base-requirements.txt	Upgraded several packages, including acryl-datahub-classify to 0.0.11 and acryl-sqlglot to 25.3.1.dev3. Introduced Azure-related libraries and renamed sql-metadata to sql_metadata.
docker/docker-compose.yml, docker/docker-compose-with-cassandra.yml, docker/docker-compose-without-neo4j.yml, docker/profiles/docker-compose.prerequisites.yml	Updated image specifications to utilize environment variables for versioning instead of hardcoded values, improving maintainability across different environments.
docker/datahub-ingestion-base/build.gradle, docker/datahub-ingestion/build.gradle	Incremented revision variable from 3 to 4 to trigger project rebuild, ensuring up-to-date components.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant PackageManager
    participant DockerCompose

    User->>App: Request updated environment setup
    App->>PackageManager: Check for package updates
    PackageManager-->>App: List of available updates
    App->>PackageManager: Upgrade selected packages
    PackageManager-->>App: Confirmation of upgrades
    App->>DockerCompose: Update image specifications
    DockerCompose-->>App: Configuration updated
    App-->>User: Environment ready with upgrades

Loading

🐇✨ In the garden where changes bloom,
Packages sprout, dispelling gloom!
Azure skies and tools so bright,
Upgrades dance, a joyful sight!
With every hop and every cheer,
Our code grows strong, no room for fear!
Let's code ahead, with hearts so light! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1955c05 and b894e2b.

Files selected for processing (1)

• docker/datahub-ingestion-base/base-requirements.txt (13 hunks)

Additional comments not posted (10)

docker/datahub-ingestion-base/base-requirements.txt (10)

50-50: Verify the compatibility of cachetools version 5.4.0.

Ensure that the new version does not introduce breaking changes or deprecations.

---

111-111: Verify the compatibility of google-api-core version 2.19.1.

Ensure that the new version does not introduce breaking changes or deprecations.

---

53-53: Verify the compatibility of certifi version 2024.7.4.

Ensure that the new version does not introduce breaking changes or deprecations.

---

129-129: Verify the compatibility of grpcio version 1.65.2.

Ensure that the new version does not introduce breaking changes or deprecations.

---

2-2: Verify the compatibility of acryl-datahub-classify version 0.0.11.

Ensure that the new version does not introduce breaking changes or deprecations.

---

6-7: Verify the compatibility of aiohttp version 3.10.0 and addition of aiohappyeyeballs version 2.3.2.

Ensure that the new version of aiohttp does not introduce breaking changes or deprecations. Verify the addition of aiohappyeyeballs and its compatibility with aiohttp.

---

112-112: Verify the compatibility of google-auth version 2.32.0.

Ensure that the new version does not introduce breaking changes or deprecations.

Verification successful

Verify the usage of google-auth version 2.32.0 in the codebase.

We need to ensure that the upgrade to version 2.32.0 does not introduce any breaking changes or deprecations.

---

Verify the compatibility of google-auth version 2.32.0.

We need to ensure that the upgrade to version 2.32.0 does not introduce any breaking changes or deprecations.

---

Verify the compatibility of google-auth version 2.32.0.

We need to ensure that the upgrade to version 2.32.0 does not introduce any breaking changes or deprecations.

---

Verify the compatibility of google-auth version 2.32.0.

We need to ensure that the upgrade to version 2.32.0 does not introduce any breaking changes or deprecations.

---

The upgrade to google-auth version 2.32.0 is safe.

The changelog for version 2.32.0 indicates that the only change is the addition of support for the X509 workload credential type, which does not introduce any breaking changes or deprecations.

• No breaking changes or deprecations were found in the changelog.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the compatibility of `google-auth` version `2.32.0`.

# Test: Check the changelog or release notes for `google-auth` version `2.32.0`.
# Expect: No breaking changes or deprecations.
curl -s https://pypi.org/project/google-auth/2.32.0/ | grep -i 'changelog\|release notes'

Length of output: 91

---

Script:

#!/bin/bash
# Search for references to `google-auth` in the codebase to identify where it is used.
rg --context 5 'google-auth'

Length of output: 866

---

Script:

#!/bin/bash
# Fetch the changelog or release notes for `google-auth` version `2.32.0` from GitHub.
curl -s https://raw.githubusercontent.com/googleapis/google-auth-library-python/main/CHANGELOG.md | grep -A 20 '## [2.32.0]'

Length of output: 9124

---

Script:

#!/bin/bash
# Fetch the changelog for `google-auth` versions `2.31.0` and `2.32.0` from GitHub.
curl -s https://raw.githubusercontent.com/googleapis/google-auth-library-python/main/CHANGELOG.md | grep -A 20 '## [2.31.0]'
curl -s https://raw.githubusercontent.com/googleapis/google-auth-library-python/main/CHANGELOG.md | grep -A 20 '## [2.32.0]'

Length of output: 27388

---

Script:

#!/bin/bash
# Fetch the specific section of the changelog for `google-auth` version `2.32.0` from GitHub.
curl -s https://raw.githubusercontent.com/googleapis/google-auth-library-python/main/CHANGELOG.md | sed -n '/## \[2.32.0\]/,/## \[2.33.0\]/p'

Length of output: 108259

---

375-375: Verify the compatibility and security of Werkzeug version 2.2.3.

Ensure that the downgrade does not introduce compatibility issues or security vulnerabilities.

---

321-321: Verify the compatibility of sql_metadata version 2.12.0 and impact of renaming.

Ensure that the new version does not introduce breaking changes or deprecations. Verify the impact of the package renaming.

---

4-4: Verify the compatibility of acryl-sqlglot version 25.3.1.dev3.

Ensure that the new version does not introduce breaking changes or deprecations.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b894e2b and ab85f6b.

Files selected for processing (4)

• docker/docker-compose-with-cassandra.yml (3 hunks)
• docker/docker-compose-without-neo4j.yml (3 hunks)
• docker/docker-compose.yml (3 hunks)
• docker/profiles/docker-compose.prerequisites.yml (1 hunks)

Additional comments not posted (10)

docker/docker-compose-without-neo4j.yml (3)

126-126: LGTM!

The change to use environment variables for the schema-registry image is correctly implemented and enhances configurability.

---

141-141: LGTM!

The change to use environment variables for the broker image is correctly implemented and enhances configurability.

---

158-158: LGTM!

The change to use environment variables for the zookeeper image is correctly implemented and enhances configurability.

docker/docker-compose-with-cassandra.yml (3)

147-147: LGTM!

The change to use environment variables for the schema-registry image is correctly implemented and enhances configurability.

---

162-162: LGTM!

The change to use environment variables for the broker image is correctly implemented and enhances configurability.

---

180-180: LGTM!

The change to use environment variables for the zookeeper image is correctly implemented and enhances configurability.

docker/docker-compose.yml (3)

146-146: LGTM!

The change to use environment variables for the schema-registry image is correctly implemented and enhances configurability.

---

161-161: LGTM!

The change to use environment variables for the broker image is correctly implemented and enhances configurability.

---

178-178: LGTM!

The change to use environment variables for the zookeeper image is correctly implemented and enhances configurability.

docker/profiles/docker-compose.prerequisites.yml (1)

213-213: LGTM! Verify environment variable documentation.

The change to use environment variable substitution for the Kafka image and version is approved. This enhances configurability and maintainability.

Ensure that the environment variables DATAHUB_CONFLUENT_KAFKA_IMAGE and DATAHUB_CONFLUENT_VERSION are documented and used correctly in the environment setup.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ab85f6b and be111f3.

Files selected for processing (2)

• docker/datahub-ingestion-base/build.gradle (1 hunks)
• docker/datahub-ingestion/build.gradle (1 hunks)

Files skipped from review due to trivial changes (2)

• docker/datahub-ingestion-base/build.gradle
• docker/datahub-ingestion/build.gradle