cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
No description
35267 commits 47 branches 390 tags 440 MiB
Python 88.4%
PowerShell 7.5%
Shell 2%
C# 1.9%
Makefile 0.1%
Find a file
Dag Wieers cf1f7b53df win_setup: Add Product ID and Product Key in facts (#34097) 
* win_setup: Add Product ID and Product Key in facts

So this is actually a very nice way to get product key information from
systems collected centrally.

Especially with systems that have been upgraded from Windows 7 or
Windows 8 to Windows 10 may not have a valid Windows 10 product
license key printed anywhere, it was a digital license.

If you ever have to reinstall the system, you may recover the system
from the recovery partition, or the original media, but cannot upgrade
to Windows 10 for free. By collecting the product key, one can always
reinstall your free Windows upgrade.

My only question is, do we want this to be part of the default facts, as
it may be considered important information. Or should we make a special
**win_product_key_facts** ?

* Add ACPI product key support
2018-01-22 16:00:45 -05:00
.github infoblox (#35179) 2018-01-22 08:25:06 -05:00
bin Error early if executing python version doesn't meet documented minimums (#34655) 2018-01-09 16:17:55 -06:00
contrib consul_io: fixed service availability check (#34293) 2018-01-19 16:33:52 -05:00
docs win_become: another option to support become flags for runas (#34551) 2018-01-19 13:58:10 -08:00
examples Update example uptime script to provide correct type for explicit individual hosts (#34740) 2018-01-16 11:39:15 -06:00
hacking Facts distribution clear linux 31501 (#32453) 2018-01-20 15:05:53 -05:00
lib/ansible win_setup: Add Product ID and Product Key in facts (#34097) 2018-01-22 16:00:45 -05:00
licenses
packaging [new module] Add Azure Container Instance support - cloud/azure/azure_rm_containerinstance (#32025) 2018-01-17 10:05:45 +10:00
test Uninstall backports.lzma in archive test. 2018-01-22 12:36:03 -08:00
ticket_stubs add bug_internal_api.md to ticket_stubs (#34370) 2018-01-03 09:46:10 -06:00
.coveragerc
.gitattributes
.gitignore
.gitmodules
.mailmap Fix syntax typo 2017-12-24 12:16:17 +01:00
.yamllint Add module support to yamllint sanity test. (#34964) 2018-01-16 15:08:56 -08:00
ansible-core-sitemap.xml Remove remnants of obsolete fireball mode. 2016-12-09 16:56:34 -07:00
CHANGELOG.md changelog: add new modules to changelog (#35158) 2018-01-22 12:18:50 +00:00
CODING_GUIDELINES.md
CONTRIBUTING.md
COPYING
docsite_requirements.txt
Makefile
MANIFEST.in
MODULE_GUIDELINES.md
README.md
RELEASES.txt updated from stable.24 2018-01-04 13:35:15 -05:00
requirements.txt
ROADMAP.rst
setup.py
shippable.yml Split Windows tests into 4 groups. 2018-01-12 00:48:32 -08:00
tox.ini
VERSION

README.md

PyPI version Build Status

Ansible

Ansible is a radically simple IT automation system. It handles configuration-management, application deployment, cloud provisioning, ad-hoc task-execution, and multinode orchestration - including trivializing things like zero downtime rolling updates with load balancers.

Read the documentation and more at https://ansible.com/

You can find installation instructions here for a variety of platforms. Most users should probably install a released version of Ansible from pip, a package manager or our release repository. Officially supported builds of Ansible are also available. Some power users run directly from the development branch - while significant efforts are made to ensure that devel is reasonably stable, you're more likely to encounter breaking changes when running Ansible this way.

Design Principles

  • Have a dead simple setup process and a minimal learning curve
  • Manage machines very quickly and in parallel
  • Avoid custom-agents and additional open ports, be agentless by leveraging the existing SSH daemon
  • Describe infrastructure in a language that is both machine and human friendly
  • Focus on security and easy auditability/review/rewriting of content
  • Manage new remote machines instantly, without bootstrapping any software
  • Allow module development in any dynamic language, not just Python
  • Be usable as non-root
  • Be the easiest IT automation system to use, ever.

Get Involved

  • Read Community Information for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
  • All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use git rebase vs git merge for this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed.
  • Users list: ansible-project
  • Development list: ansible-devel
  • Announcement list: ansible-announce - read only
  • irc.freenode.net: #ansible

Branch Info

  • Releases are named after Led Zeppelin songs. (Releases prior to 2.0 were named after Van Halen songs.)
  • The devel branch corresponds to the release actively under development.
  • Various release-X.Y branches exist for previous releases.
  • We'd love to have your contributions, read Community Information for notes on how to get started.

Authors

Ansible was created by Michael DeHaan (michael.dehaan/gmail/com) and has contributions from over 1000 users (and growing). Thanks everyone!

Ansible is sponsored by Ansible, Inc

License

GNU General Public License v3.0

See COPYING to see the full text.