Skip to content

Conversation

@mfuhrmann
Copy link
Contributor

All Contributors

Contribution Checklist

  • Please make an issue in the OpenNMS issue tracker if there isn't one already.
    Once there is an issue, please:
    1. update the title of this PR to be in the format: ${JIRA-ISSUE-NUMBER}: subject of pull request
    2. update the Jira link at the bottom of this comment to refer to the real issue number
    3. prefix your commit messages with the issue number, if possible
    4. once you've created this PR, please link to it in a comment in the Jira issue
      Don't worry if this sounds like a lot, we can help you get things set up properly.
  • If this code is likely to affect the UI, did you name your branch with -smoke in it to trigger smoke tests?
  • If this is a new or updated feature, is there documentation for the new behavior?
  • If this is new code, are there unit and/or integration tests?
  • If this PR targets a foundation-* branch, does it try to avoid changing files in $OPENNMS_HOME/etc/?

What's Next?

A PR should be assigned at least 2 reviewers. If you know that someone would be a good person to review your code, feel free to add them.

If you need help making additions or changes to the documentation related to your changes, please let us know.

In any case, if anything is unclear or you want help getting your PR ready for merge, please don't hesitate to say something in the comments here,
or in the #opennms-development chat channel.

Once reviewer(s) accept the PR and the branch passes continuous integration, the PR is eligible for merge.

At that time, if you have commit access (are an OpenNMS Group employee or a member of the OGP) you are welcome to merge the PR when you're ready.
Otherwise, a reviewer can merge it for you.

Thanks for taking time to contribute!

External References

@github-actions github-actions bot added the docs label Jan 29, 2026
@mfuhrmann
Copy link
Contributor Author

mfuhrmann commented Jan 29, 2026

I tried to get Debian/Ubuntu and Centos/RHEL docs merged and it looks good so far. They work for U24/D13 and CentOS 9/10.

I've noticed that the Postgresql version variable does not get resolved in the Debian/Ubuntu tree. Not sure why.
Also, I had to change a bit the backup/restore docs because Antora was not happy. I need to test these docs again with all the OS versions.

Also, the Minion and Sentinel docs were just adapted to make Antora happy, but they are not tested, yet. I've seen there install commands for openjdk for example that we do not need, if we always use Temurin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant