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

Telemetry Improvement: Bicep Params #7825

Closed
3 tasks
ucheNkadiCode opened this issue Aug 3, 2022 · 3 comments
Closed
3 tasks

Telemetry Improvement: Bicep Params #7825

ucheNkadiCode opened this issue Aug 3, 2022 · 3 comments
Labels

Comments

@ucheNkadiCode
Copy link
Contributor

ucheNkadiCode commented Aug 3, 2022

Related to #7301

Order of priority

  • 1. Param file open (top of funnel)
  • 2. Param file save event
  • 3. Add the paramfile type to deploy command (we can finalize the design later)

If we wrap this event into other snippet events, we will still need to add an attribute like fileType "BicepParam" in order differentiate between our regular bicep files.

@sydkar for opinion and comments

@sydkar
Copy link

sydkar commented Aug 5, 2022

I think these sound good. We might want to track the number of deployments or builds done with .bicepparam files as well. As additional features become available, we should probably add items to this list., especially those that are more experimental.

@alex-frankel
Copy link
Collaborator

Are there other metrics that demonstrate usage (editing bicepparam files) besides tab completions?

@stephaniezyen
Copy link
Contributor

Reopen with specific scenarios to capture

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants