Skip to content
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

Don't redact env tokens from DI probe snapshots #3827

Merged
merged 1 commit into from
Jan 15, 2025
Merged

Conversation

watson
Copy link
Contributor

@watson watson commented Jan 15, 2025

Motivation

Feature parity

Changes

Remove env from list of tokens to redact from Dynamic Instrumentation probe snapshots

Workflow

  1. ⚠️ Create your PR as draft ⚠️
  2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
  3. Mark it as ready for review
    • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
    • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

  • If PR title starts with [<language>], double-check that only <language> is impacted by the change
  • No system-tests internal is modified. Otherwise, I have the approval from R&P team
  • CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
  • A docker base image is modified?
    • the relevant build-XXX-image label is present
  • A scenario is added (or removed)?

@watson watson marked this pull request as ready for review January 15, 2025 14:52
@watson watson requested review from a team as code owners January 15, 2025 14:52
Copy link
Contributor Author

watson commented Jan 15, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@watson watson merged commit 2cb5033 into main Jan 15, 2025
281 checks passed
@watson watson deleted the watson/env-redaction branch January 15, 2025 16:02
watson added a commit that referenced this pull request Jan 16, 2025
This has already been removed in the PII test file in the following PR:

    #3827
dudikeleti pushed a commit to DataDog/dd-trace-dotnet that referenced this pull request Jan 17, 2025
## Summary of changes

Remove `env` from list of tokens to redact from Dynamic Instrumentation
probe snapshots.

Depends on: DataDog/system-tests#3827

## Reason for change

Feature parity

## Implementation details

## Test coverage

## Other details
<!-- Fixes #{issue} -->

<!-- ⚠️ Note: where possible, please obtain 2 approvals prior to
merging. Unless CODEOWNERS specifies otherwise, for external teams it is
typically best to have one review from a team member, and one review
from apm-dotnet. Trivial changes do not require 2 reviews. -->
P403n1x87 pushed a commit to DataDog/dd-trace-py that referenced this pull request Jan 21, 2025
## Summary of changes

Remove `env` from list of tokens to redact from Dynamic Instrumentation
probe snapshots.

Depends on: DataDog/system-tests#3827

## Reason for change

Feature parity

## Checklist
- [x] PR author has checked that all the criteria below are met
- The PR description includes an overview of the change
- The PR description articulates the motivation for the change
- The change includes tests OR the PR description describes a testing
strategy
- The PR description notes risks associated with the change, if any
- Newly-added code is easy to change
- The change follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
- The change includes or references documentation updates if necessary
- Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist
- [x] Reviewer has checked that all the criteria below are met 
- Title is accurate
- All changes are related to the pull request's stated goal
- Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes
- Testing strategy adequately addresses listed risks
- Newly-added code is easy to change
- Release note makes sense to a user of the library
- If necessary, author has acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment
- Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
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.

2 participants