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

We should verify if analytics is disabled upon container start #11

Closed
tuxmea opened this issue Oct 13, 2023 · 5 comments · Fixed by #53
Closed

We should verify if analytics is disabled upon container start #11

tuxmea opened this issue Oct 13, 2023 · 5 comments · Fixed by #53

Comments

@tuxmea
Copy link
Member

tuxmea commented Oct 13, 2023

No description provided.

@rwaffen
Copy link
Member

rwaffen commented Oct 13, 2023

the pupperware analytics are now removed completely with the remove of the 01-analytics.sh. as far as i know.

@tuxmea
Copy link
Member Author

tuxmea commented Oct 14, 2023

Analytics from Puppet are usually opt-out! Just removing them might not be sufficient.

@rwaffen
Copy link
Member

rwaffen commented Nov 8, 2023

okay. pupperware had it's own analytics, but you talk about the service internal analytics from puppetdb/server.
that we have to check, yes.

@rwaffen
Copy link
Member

rwaffen commented Nov 9, 2023

Analytics are not implemented in OSS. There is only an update-check.

@rwaffen
Copy link
Member

rwaffen commented Dec 12, 2023

have to look for dropsonde

links to: voxpupuli/container-puppetserver#7

@rwaffen rwaffen moved this to In Progress in Crafty Overview Mar 15, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Crafty Overview Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants