011d240abc
When subscribing a system with an activationkey, it seems (sometimes?) required to pass the "--org <number>" parameter to subscription-manager. Activation Keys can be created through the Red Hat Customer Portal, and a subscription can be attached to those. This makes is easy to register systems without passing username/passwords around. The organisation ID can be retrieved by executing the following command on a registered system (*not* the account number): # subscription-manager identity URL: https://access.redhat.com/management/activation_keys Signed-off-by: Niels de Vos <ndevos@redhat.com> Reviewed-by: Ken Dreyer <kdreyer@redhat.com> |
||
|---|---|---|
| cloud | ||
| commands | ||
| database | ||
| files | ||
| inventory | ||
| network | ||
| packaging | ||
| source_control | ||
| system | ||
| utilities | ||
| web_infrastructure | ||
| windows | ||
| .gitignore | ||
| __init__.py | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| README.md | ||
ansible-modules-core
This repo contains Ansible's most popular modules that are shipped with Ansible.
New module submissions for modules that do not yet exist should be submitted to ansible-modules-extras, rather than this repo.
Take care to submit tickets to the appropriate repo where modules are contained. The docs.ansible.com website indicates this at the bottom of each module documentation page.
Reporting bugs
Take care to submit tickets to the appropriate repo where modules are contained. The repo is mentioned at the bottom of module documentation page at docs.ansible.com.
Testing modules
Ansible module development guide contains the latest info about that.
License
As with Ansible, modules distributed with Ansible are GPLv3 licensed. User generated modules not part of this project can be of any license.
Installation
There should be no need to install this repo separately as it should be included in any Ansible install using the official documented methods.