Do not install tab completion (edit of profile) under certain conditions

[ferventcoder]

During install, do not try to update/create the profile if an environment variable exists.

We may want to look at the execution policy for the machine and respond accordingly to not automatically installing the profile unless it meets a minimum level to reduce issues with running PowerShell later.

• Do not create profile if it doesn't already exist.
• Do not set profile if user is SYSTEM.
• Do not create set profile if $env:ChocolateyNoProfile exists.
• Don't edit the profile if it is authenticode signed.

[RedBaron2]

@ferventcoder Wouldn't something like this work the best.

Install-ChocolateyEnvironmentVariable -variableName "ChocolateyProfile" -variableValue {true/false}

This is then checked by function Add-ChocolateyProfile for {true/false}

The only thing I see as an issue will be those that had the profile installed previously without the environment variable. I might suggest they add the variable to windows manually ( I know not exactly automated )

The alternative is to just add a chocolatey cmd line switch when installing chocolatey.

[dragon788]

As in the above referenced issue, this is causing "failures" in the vagrant-dsc plugin due to an extra "Preparing modules for first use" message that appears if the Chocolatey created profile exists, but only with PowerShell 5. The temporary workaround has been to remove the $profile during a script provision before the plugin attempts to run its own provisioning.

[ferventcoder]

I think we are just going to pull this from the installer and move to an additional command to install/uninstall the profile.