-
Notifications
You must be signed in to change notification settings - Fork 15
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
Explicitly document how to register to Red Hat #142
Comments
The general RHEL documentation for the role is here: For connecting to Red Hat, there are no attributes (e.g.
I'm not sure I understand the problem here: why would you need to guess? What's the "thought process" here that might lead to confusion? |
I want to use this role to connect a system to Red Hat, not local Satellite. This is the role documentation: https://github.com/linux-system-roles/rhc. It doesn't tell what should values should be used for rhc_server in that case. |
Just like the RHEL documentation does not mention any changes needed to register to Red Hat, the same applies here to the role. What I can write is that not changing a/any parameter means that the "default" of the system, which means the underlying tool. |
I think it would be a good idea to document the default, just like the default is documented with other variables as well. Thanks. |
The role should explicitly state something like "To register to Red Hat, the - name: Register system to Red Hat
vars:
rhc:
....
roles:
- linux-system-roles.rhc |
The documentation at https://github.com/linux-system-roles/rhc discusses about
rhc_server
but doesn't give any indication what if any values should be used when connecting to Red Hat instead of a local satellite. While many might guess or test that the variable can be left undefined it'd be better to avoid guessing and mention that explicitly. Thanks.The text was updated successfully, but these errors were encountered: