-
Notifications
You must be signed in to change notification settings - Fork 61
fix(cli): running --telemetry-file without the --unstable option creates a telemetry file
#731
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
| throw new ToolkitError('You must either specify a list of Stacks or the `--all` argument'); | ||
| } | ||
|
|
||
| if (args['telemetry-file'] && !configuration.settings.get(['unstable']).includes('telemetry')) { |
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.
This is too late in the process because telemetry has already been initialized, and the error thrown is then considered as a telemetry event.
We should really structure the unstable protection mechanism better.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #731 +/- ##
==========================================
- Coverage 81.05% 81.00% -0.05%
==========================================
Files 61 61
Lines 8007 8007
Branches 900 898 -2
==========================================
- Hits 6490 6486 -4
- Misses 1497 1501 +4
Partials 20 20
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This feature is currently unstable, so it shouldn't apply at all if invoked without the
--unstableflag.Right now, it creates a telemetry file with an event indicating the aforementioned failure.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license