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

(maint) Turn off analytics submissions #3294

Merged
merged 4 commits into from
Apr 8, 2024

Conversation

donoghuc
Copy link
Member

@donoghuc donoghuc commented Apr 2, 2024

Collecting analytics is now turned off by default.

!removal

  • Stop collecting bolt analytics (#3293)

    Bolt no longer collects analytics by default.

Collecting analytics is now turned off by default.

!removal

* **Stop collecting bolt analytics** ([puppetlabs#3293](puppetlabs#3293))

  Bolt no longer collects analytics by default.
Docker-compose does not appear to be installed on ubuntu-latest runners. Ensure it is installed before bringing up test cluster.
@donoghuc donoghuc force-pushed the disable-analytics branch 2 times, most recently from 65c4eb2 to cd44c5f Compare April 2, 2024 22:55
This is the last release that passes for building bolt docs. Pin to that version while we evaluate how to remain compatible with latest.
Copy link
Contributor

@tlehman tlehman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

We attempt to compute Execution Policy in order to provide a nice error message for some cases. We are seeing failures in some cases to compute this value. In the case the execution policy cannot be determined we still want to be able to attempt to run the action. This commit handles errors when execution policy cannot be determined.
@@ -55,21 +55,25 @@ def run_script(arguments, script_path)
}
#{build_arg_list}

switch -regex ( Get-ExecutionPolicy )
try
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mcdonaldseanp I think the path is messed up for module loading in our test runners:

       +"merged_output" => "Get-ExecutionPolicy : The 'Get-ExecutionPolicy' command was found in the module 'Microsoft.PowerShell.Security', but \r\nthe module could not be loaded. For more information, run 'Import-Module Microsoft.PowerShell.Security'.\r\nAt line:10 char:17\r\n+ switch -regex ( Get-ExecutionPolicy )\r\n+                 ~~~~~~~~~~~~~~~~~~~\r\n    + CategoryInfo          : ObjectNotFound: (Get-ExecutionPolicy:String) [], CommandNotFoundException\r\n    + FullyQualifiedErrorId : CouldNotAutoloadMatchingModule\r\n \r\nparam\n",

I think that the intent of this was simply to provide a helpful error message and that we should not error if we cant load that module. In practice i doubt this comes up much because task running all works due to other powershell setup we do.

Do you think a catch here is reasonable, should it be more specific on objects it catches?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#2659 for reference

@donoghuc donoghuc merged commit 8266293 into puppetlabs:main Apr 8, 2024
44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants