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

Inconsistent wording between "telemetry" & "usage data" #714

Open
bombguy opened this issue Nov 20, 2023 · 0 comments
Open

Inconsistent wording between "telemetry" & "usage data" #714

bombguy opened this issue Nov 20, 2023 · 0 comments
Labels
good first issue Good for newcomers tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later

Comments

@bombguy
Copy link
Contributor

bombguy commented Nov 20, 2023

Environment information

System:
    OS: macOS 13.5
    CPU: (10) arm64 Apple M1 Pro
    Memory: 574.00 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.9.0 - ~/.npm-global/bin/npm
    pnpm: Not Found
    Watchman: Not Found
  npmPackages:
    @aws-amplify/backend: Not Found
    @aws-amplify/backend-cli: Not Found
    aws-amplify: Not Found
    aws-cdk: Not Found
    aws-cdk-lib: Not Found
    typescript: ^5.0.4 => 5.2.2

Description

Throughout the codebase, the word telemetry and usage data is being used interchangeably.

List of some of the inconsistency

  • subcommand to configure telemetry: amplify configure telemetry enable|disable
  • ENV_VAR to override telemetry preference: AMPLIFY_DISABLE_TELEMETRY
  • local config file content: { telemetry: { enabled: false } }
  • links to doc: https://docs.amplify.aws/gen2/reference/telemetry
  • content under platform-core/src/usage-data
@bombguy bombguy added the pending-triage Incoming issues that need categorization label Nov 20, 2023
@edwardfoyle edwardfoyle added tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later good first issue Good for newcomers and removed pending-triage Incoming issues that need categorization labels Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later
Projects
None yet
Development

No branches or pull requests

2 participants