Skip to content

chore: remove the hardcoded 2.21.3 version in dockerfile #568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 4, 2025

Conversation

joeyzhao2018
Copy link
Contributor

@joeyzhao2018 joeyzhao2018 commented Mar 4, 2025

What does this PR do?

We had to release a datadog-lambda-py layer with ddtrace 2.21.3 before releasing a layer with ddtrace v3. Related PR: #565
Now reverting the hardcoded ddtrace version in the docker file.

Motivation

Testing Guidelines

Additional Notes

Types of Changes

  • Bug fix
  • New feature
  • Breaking change
  • Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

  • This PR's description is comprehensive
  • This PR contains breaking changes that are documented in the description
  • This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
  • This PR impacts documentation, and it has been updated (or a ticket has been logged)
  • This PR's changes are covered by the automated tests
  • This PR collects user input/sensitive content into Datadog
  • This PR passes the integration tests (ask a Datadog member to run the tests)

@joeyzhao2018 joeyzhao2018 requested a review from a team as a code owner March 4, 2025 20:31
Co-authored-by: datadog-datadog-prod-us1[bot] <88084959+datadog-datadog-prod-us1[bot]@users.noreply.github.com>
@mabdinur mabdinur changed the title remove the hardcoded 2.21.3 version in dockerfile chore: remove the hardcoded 2.21.3 version in dockerfile Mar 4, 2025
Copy link
Collaborator

@mabdinur mabdinur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we update the PR description to include why we needed to hard the ddtrace version

@@ -14,7 +14,7 @@ ENV PATH=/root/.cargo/bin:$PATH

# Install datadog_lambda and dependencies from local
COPY . .
RUN pip install . ddtrace==2.21.3 -t ./python/lib/$runtime/site-packages
RUN pip install --no-cache-dir . -t ./python/lib/$runtime/site-packages
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this safe to do? What's the implication of this? Do you remember why we were pinning before?

There was a pretty good reason about this from the past

Copy link
Contributor Author

@joeyzhao2018 joeyzhao2018 Mar 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for ddtrace==2.21.3 it's in the description.
For --no-cache-dir... i actually wonder how it was added ... my local change didn't have it just realized that @mabdinur merged the bot suggestion :P

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, that's the reason, you were pinning in the past you wanted to make sure the fix was included for dynamodb, sg

@joeyzhao2018 joeyzhao2018 merged commit d9cf9fa into main Mar 4, 2025
59 checks passed
@joeyzhao2018 joeyzhao2018 deleted the joey/fix-dockerfile branch March 4, 2025 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants