-
Notifications
You must be signed in to change notification settings - Fork 90
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
Use global registration after renaming Smart Proxy Server #3033
Use global registration after renaming Smart Proxy Server #3033
Conversation
maximiliankolb
commented
May 16, 2024
- I am familiar with the contributing guidelines.
The PR preview for 423cc65 is available at theforeman-foreman-documentation-preview-pr-3033.surge.sh The following output files are affected by this PR: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
2f65977
to
dd62652
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think global registration should be used to re-register. I'd much prefer a REX job to update the existing registration. Though I'm not 100% sure we have such a job already
This comment was marked as outdated.
This comment was marked as outdated.
I am creating a proper way to replace Foreman's CA in this pr: theforeman/foreman#10208 |
dd62652
to
ab482a7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebased to "master", resolved all merge conflicts, and applied all suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small style comment. Otherwise, LGTM.
---- | ||
endif::[] | ||
endif::[] | ||
. Re-register all hosts that are registered to your {SmartProxyServer}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very small nit-pick. Our downstream guidelines say this about hyphenated prefixes:
"In most cases, do not use a hyphen to connect a prefix or suffix to a word. There are cases where a hyphen between a prefix and root word adds clarity. For more information, see ..."
We do not yet have a Vale rule to flag "pre-", "post-", "re-", etc. I think this might be a good rule to add. :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correction: We do have a Vale rule. It does not include "re-register", so I created a PR to fix this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Applied.
ab482a7
to
423cc65
Compare