Adding a little more context on how we've talked about doing this:
Many of our release channels create their own launcher script. We do this to accommodate different manners of acquiring Python. However, we can take advantage of this by setting an environment variable as we invoke the CLI.

Take our RPM spec for example:

azure-cli/scripts/release/rpm/azure-cli.spec

Line 69 in e241fd5

    
           printf '#!/usr/bin/env bash\n%{cli_lib_dir}/bin/python -Esm azure.cli "$@"' > %{buildroot}%{_bindir}/az

would become:

printf '#!/usr/bin/env bash\nAZ_INSTALLER=RPM %{cli_lib_dir}/bin/python -Esm azure.cli "$@"' > %{buildroot}%{_bindir}/az

In Homebrew, our launcher would go from:

azure-cli/scripts/release/homebrew/docker/formula_template.txt

Lines 39 to 42 in a3cad86

    
           (bin/"az").write <<~EOS 
        
             #!/usr/bin/env bash 
        
             #{libexec}/bin/python -m azure.cli \"$@\" 
        
           EOS

to:

    (bin/"az").write <<~EOS
      #!/usr/bin/env bash
      AZ_INSTALLER=brew #{libexec}/bin/python -m azure.cli \"$@\"
    EOS

We could then take the value of AZ_INSTALLER and append it to our user agent.

	(bin/"az").write <<~EOS
	#!/usr/bin/env bash
	#{libexec}/bin/python -m azure.cli \"$@\"
	EOS

telemetry: include Azure CLI acquisition information in the user-agent #9013

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions