1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Find a file
Adam Miller 75127092f2 refactor firewalld module with object abstraction (#26487)
* refactor firewalld module with object abstraction

This change creates a FirewallTransaction object that each
individual transaction type is a sub-class of as they all follow the
same pattern to enable or disable something in the firewall.

Also, there's a few bugfixes here:
    - Fix the "source" type to handle permanent operations
    - Remove ambiguity of required parameters for only specific use
      cases that can lead to transactions effectively being a no-op.
      Instead, pick sane defaults and document them.
    - Change how imports are done so globals are no longer needed

This is based on the original feedback by Toshio from the last
refactor attempt:

    https://github.com/ansible/ansible-modules-extras/pull/3383

Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>

* fix line too long for pep8 for shippable tests

Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>

* remove firewalld from pep8/legacy-files

Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>
2017-09-11 14:10:07 -07:00
.github Remove test/: key since it is now empty (#29660) 2017-09-11 15:21:14 -04:00
bin Create persistent socket path using port and connection type (#28492) 2017-08-23 18:28:44 -04:00
contrib Handle missing docker-py better (#27540) 2017-09-10 19:06:57 -07:00
docs Remove use of unicode_literals as it is an anti-pattern 2017-09-11 13:33:51 -07:00
examples fixed typo 2017-08-29 11:49:29 -04:00
hacking [cloud] Update RDS parameter group for boto3 (#25345) 2017-08-28 12:52:22 -04:00
lib/ansible refactor firewalld module with object abstraction (#26487) 2017-09-11 14:10:07 -07:00
packaging Bump the versions now that devel is 2.5 2017-09-06 13:13:57 -07:00
test refactor firewalld module with object abstraction (#26487) 2017-09-11 14:10:07 -07:00
ticket_stubs Remove obsolete ticket stubs. 2016-12-08 11:35:20 -05:00
.coveragerc Docker image updates for integration tests. (#26054) 2017-06-23 12:45:38 -07:00
.gitattributes avoid exporting files useless to dist 2017-06-23 15:56:43 -04:00
.gitignore Ignore autogenerated _maintained.rst and config.rst (#28925) 2017-09-01 15:15:45 +01:00
.gitmodules Code cleanup. 2016-12-08 11:35:04 -05:00
.mailmap add mailmap entries for @resmo 2017-04-09 11:56:37 +02:00
.yamllint Lint YAML files under test/ 2016-11-11 14:50:57 -08:00
ansible-core-sitemap.xml Remove remnants of obsolete fireball mode. 2016-12-09 16:56:34 -07:00
CHANGELOG.md remove fact namespacing 2017-09-10 17:37:52 -04:00
CODING_GUIDELINES.md Use pycodestyle instead of pep8 (#25947) 2017-07-13 11:46:31 -07:00
CONTRIBUTING.md Update CONTRIBUTING.md with more recent developments 2016-03-23 15:32:29 +01:00
COPYING license file should be in source tree 2012-03-15 20:24:22 -04:00
docsite_requirements.txt Fixes the build issue pertaining to sphinx-build which is required to build ansible (#22480) 2017-03-14 14:19:46 -07:00
Makefile generate rst doc pages for command line tools (#27530) 2017-09-07 15:44:20 -04:00
MANIFEST.in powershell setup fixes (#27516) 2017-07-31 12:16:26 -07:00
MODULE_GUIDELINES.md Add a direct link to the maintainer's file (#26450) 2017-07-06 09:19:27 +01:00
README.md Fix installation instructions link in the README (#24754) 2017-05-18 08:09:53 +01:00
RELEASES.txt Updating RELEASES and packaging vars for 2.3.2 final release 2017-08-04 15:20:41 -05:00
requirements.txt Cyptography pr 20566 rebase (#25560) 2017-06-27 06:00:15 -07:00
ROADMAP.rst docs: fix community meetings link (#27264) 2017-07-25 09:23:01 -04:00
setup.py On Py3, nonexistent files raise OSError (#28899) 2017-08-31 17:47:26 -04:00
shippable.yml Revert "Temporarily disable failing opensuse test jobs." 2017-09-07 11:47:53 -07:00
tox.ini Update tox.ini to use ansible-test. 2017-06-30 16:41:30 -07:00
VERSION Bump the versions now that devel is 2.5 2017-09-06 13:13:57 -07:00

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/

Many users run straight from the development branch (it's generally fine to do so), but you might also wish to consume a release.

You can find instructions here for a variety of platforms.

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.
  • For releases 1.8 - 2.2, modules are kept in different repos, you'll want to follow core and extras
  • 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

Licence

GNU Click on the Link to see the full text.