-
Notifications
You must be signed in to change notification settings - Fork 45
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
Conversation
Co-authored-by: datadog-datadog-prod-us1[bot] <88084959+datadog-datadog-prod-us1[bot]@users.noreply.github.com>
There was a problem hiding this 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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 just realized that @mabdinur merged the bot suggestion :P--no-cache-dir
... i actually wonder how it was added ... my local change didn't have it
There was a problem hiding this comment.
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
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
Check all that apply