generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 176
Closed
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedgood-first-issueSomething that is suitable for those who want to start contributingSomething that is suitable for those who want to start contributinginternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)tracerThis item relates to the Tracer UtilityThis item relates to the Tracer Utility
Milestone
Description
Bug description
More of a chore than a bug but the Tracer utility is called "Tracer" everywhere except than in the name of its containing folder.
This inconsistency causes annoyance and confusion, especially dealing with Github Actions.
Expected Behavior
Rename the current folder of the Tracer utility from:
packages/tracing
to
packages/tracer
Current Behavior
N/A
Possible Solution
N/A
Steps to Reproduce
N/A
Environment
- Powertools version used: all
- Packaging format (Layers, npm): NPM
- AWS Lambda function runtime: N/A
- Debugging logs: N/A
Related issues, RFCs
N/A
Metadata
Metadata
Assignees
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedgood-first-issueSomething that is suitable for those who want to start contributingSomething that is suitable for those who want to start contributinginternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)tracerThis item relates to the Tracer UtilityThis item relates to the Tracer Utility