8000 Properly maintain this repo · Issue #10 · netdata/ansible · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Properly maintain this repo #10

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

Open
6 tasks
tkatsoulas opened this issue Sep 15, 2023 · 2 comments · May be fixed by #16
Open
6 tasks

Properly maintain this repo #10

tkatsoulas opened this issue Sep 15, 2023 · 2 comments · May be fixed by #16

Comments

@tkatsoulas
Copy link
Contributor
tkatsoulas commented Sep 15, 2023

We are gonna to rework this repo (playbook) so the end goal is; users to easily deploy netdata via ansible

Tasks:

  • Change the ship of packages, from package cloud to repo.netdata.cloud
  • Sync the supported native packages with https://github.com/netdata/netdata/blob/master/.github/data/distros.yml
  • Figure out an option to install and execute any action (role) for not supported versions (via static builds)
  • Create test for most of the actions/plays
  • Create plays (roles or something else) to manage any config file of netdata
  • Publish this playbook to ansible galaxy
@luisj1983
Copy link
Contributor
luisj1983 commented Sep 21, 2023

Here are some additional near-term suggestions:

  • Update documentation (readme's are boiler-plate)
  • Mechanism to handle API (grab key, use key locally)
    • Role for silencing alarms (Maintenance Mode)
  • Consider properly splitting out roles for better Molecule compatibility and safer use of playbook tags

@pid1 pid1 linked a pull request Jan 15, 2025 that will close this issue
@ralphm
685F Copy link
Member
ralphm commented Jan 22, 2025

We've working with a user on doing a rewrite of the Ansible roles: #16. I am in the process of reviewing this as a basis for the work required for this ticket.

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 a pull request may close this issue.

3 participants
0