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
refactor: prepare for 10.7.0 release #1097
Conversation
if slices.Contains(data.Args, "--metadata-enable") && !metadataDisable && !data.Config.CLI.MetadataNoticeDisplayed && commandCollectsData(commandName) { | ||
text.Important(data.Output, "The Fastly CLI is configured to collect data related to Wasm builds (e.g. compilation times, resource usage, and other non-identifying data). To learn more about our data & privacy policies visit https://www.fastly.com/trust. Join the conversation https://bit.ly/wasm-metadata") | ||
if !slices.Contains(data.Args, "--metadata-disable") && !metadataDisable && !data.Config.CLI.MetadataNoticeDisplayed && commandCollectsData(commandName) { | ||
text.Important(data.Output, "The Fastly CLI is configured to collect data related to Wasm builds (e.g. compilation times, resource usage, and other non-identifying data). To learn more about what data is being collected, why, and how to disable it: https://developer.fastly.com/reference/cli/") |
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.
@jaskiratr you'll need to ensure the DevHub has the relevant content there ready to go once we publish the new release.
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.
I created a PR for the DevHub content.
I can also create a separate PR to take down the the Important
notice on these pages https://developer.fastly.com/reference/cli/
https://developer.fastly.com/learning/tools/cli
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.
Created a PR for removing the Important
notice from the CLI pages.
Code wise this looks good to me.
Which feels a bit strange -- is it printing the current settings, updating them to enable the build and package information, something else? why is it saying the configuration was updated? -- but perhaps it is aligned with other subcommands. Also, I'd like the (optional) flags to be more prominent; this behaviour is highly contentious so IMO things need to be very evident and explicit. |
25b46ab
to
058901a
Compare
dfb7a1b
to
a4dbd87
Compare
@fgsch I've resolved the issue you mentioned. Thanks for raising that! @jaskiratr I'm going to add an option for disabling the script info data collection (e.g. the |
OK I've pushed up changes to support disabling script_info. I think this PR is good to be merged. |
No description provided.