Skip to content
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

create ansible.github.com #2

Closed
mpdehaan opened this Issue Mar 6, 2012 · 1 comment

Comments

Projects
None yet
1 participant
@mpdehaan
Copy link
Contributor

mpdehaan commented Mar 6, 2012

No description provided.

@mpdehaan

This comment has been minimized.

Copy link
Contributor Author

mpdehaan commented Mar 8, 2012

done

@mpdehaan mpdehaan closed this Mar 8, 2012

@tbielawa tbielawa referenced this issue Jun 13, 2012

Merged

Fix author #470

mpdehaan added a commit that referenced this issue Oct 8, 2012

mpdehaan added a commit that referenced this issue Oct 8, 2012

Merge pull request #2 from skvidal/master
eucalyptus support into ec2 inventory module

mpdehaan pushed a commit that referenced this issue Oct 31, 2012

mpdehaan pushed a commit that referenced this issue Nov 20, 2012

jctanner added a commit that referenced this issue Jan 20, 2014

Merge pull request #5333 from mvermaes/yum_fix
yum module: Attempt #2 to cause yum to fail on invalid url

jimi-c pushed a commit to jimi-c/ansible that referenced this issue Jul 7, 2014

Merge pull request ansible#2 from taylorbarstow/inventorytree-tests
Adding unit tests for host groups with inventory dir

follower added a commit to follower/ansible that referenced this issue Nov 29, 2014

kbreit added a commit to kbreit/ansible that referenced this issue Jul 3, 2018

Fix vyos_vlan aggregate issue & added tests (ansible#41638)
* Fix vyos_vlan aggregate issue & Added tests

* Fix ansible#2 for vyos_vlan aggregate issue

(cherry picked from commit 837c216)

nitzmahone added a commit that referenced this issue Jul 3, 2018

Fix vyos_vlan aggregate issue & added tests CP into 2.5 (#41638) (#41775
)

* Fix vyos_vlan aggregate issue & added tests (#41638)

* Fix vyos_vlan aggregate issue & Added tests

* Fix #2 for vyos_vlan aggregate issue

(cherry picked from commit 837c216)

* Added changelog for vyos_vlan aggregate issue fix

Madhura-CSI added a commit to cambridge-semantics/ansible that referenced this issue Aug 13, 2018

felixfontein pushed a commit to felixfontein/ansible that referenced this issue Sep 30, 2018

docker_container: ambiguous parameter "stop_timeout" (ansible#43874)
* docker_container: Honour stop_timeout when creating docker containers (ansible#43814)

* Adjusting description to what actually happens.

See docker-py changelog for 2.7.0: 'APIClient.stop will
no longer override the stop_timeout value present in the
container’s configuration.'

* Add a test whether stop_timeout can be configured for the container.

* Added changelog.

* Integrate with comparisons (by default, ignore stop_timeout value for restarts; will be configurable with PR ansible#44789).

* Fix config change code and tests (ansible#2)

* Improving wildcard test.
* Using correct config.

rowshi referenced this issue in rowshi/ansible Oct 4, 2018

update fork (#1)
* fix wording for silencing a sensu client (ansible#46250)

* module/systemd: fix logic determining if a service needs to be enabled (ansible#46245)

* modules/systemd: fix logic: allow scope to default to 'system'

Fix logic introduced in 7ea9094: if 'scope' param is not specified,
it defaults to system, but the value of module.params['scope'] is None,
not 'system' - so allow for that.

* modules/systemd: fix logic: disabled means disabled

Fix logic determining whether a service with both systemd and initd files is enabled or disabled.

In situations where systemd thinks service is disabled, but rc.d symlinks mark it as enabled,
this module wrongly assumes the service is enabled.

Fix this logic: disabled means disabled

Only when the output from does NOT include disabled, consider the status of rc.d symlinks.

This essentially replicates the fixes done to the systemd handling in the "service" module in 3c89a21

Fixes ansible#22303

Fixes ansible#44409

* Corrected typo

Corrected typo
ansible_serach_path --> ansible_search_path
+label: docsite_pr

* added new module aci_access_port_block_to_access_port

* changed documentation strings

* be compliant to pep8 and pylint. Added integration tests.

* added parameter leaf_port_blk_description in module and integration tests

* added period in description. Changed integration test to work correctly.

* Use unicode instead of bytes (ansible#46234)

The stdout and stderr values returned from self._low_level_execute() are text, not bytes. This results in an error in Python 3 since str and bytes cannot be concatenated.

Changing to unicode type allows this to work without error on Python 2 and Python 3.

* Ensure _raw_params retain exact spaces

This fixes a few issues related to multi-line YAML strings that eat
whitespace and add whitespaces after newlines (that weren't there).

* Add integration tests

By checking the cmd result with the original we cause these tests to
fail on older releases without this PR.

* Add unit tests

* Add less judgmental hint to use script + template

* yes, we do run validate_modules in Shippable (ansible#46280)

* Update playbooks_delegation.rst (ansible#46254)

Fix example variable lookup.

+label: docsite_pr

* better error on empty playbook

fixes ansible#45480

* Use bytes rather than native string for result (ansible#46281)

This prevents a stack trace in Python 3 when the result is an empty file since
the file is open in binary mode and a native string in Python 3 is str,
not bytes.

* Add support for OpenBSD (ansible#46147)

* seboolean: Fix issue with changing persistent SELinux boolean values (ansible#22779)

Previously, when the active SELinux value was the same as the desired value, regardless of the value of `persistent`, the module would simply exit successfully, assuming no need for update. This made the assumption that the active and persistent values should be the same, but that is not always the case. This modification treats both the active and persistent values separately when checking for the need to update. Note that the persistent update mode, however, will still update the active as well as the persistent value. If this is not desired, it is possible to separately toggle the active value alone.

Other changes:
* Make the check mode actually perform checks for changes
* Organizes semanage commands into set of logical steps

* docker_container: ambiguous parameter "stop_timeout"  (ansible#43874)

* docker_container: Honour stop_timeout when creating docker containers (ansible#43814)

* Adjusting description to what actually happens.

See docker-py changelog for 2.7.0: 'APIClient.stop will
no longer override the stop_timeout value present in the
container’s configuration.'

* Add a test whether stop_timeout can be configured for the container.

* Added changelog.

* Integrate with comparisons (by default, ignore stop_timeout value for restarts; will be configurable with PR ansible#44789).

* Fix config change code and tests (#2)

* Improving wildcard test.
* Using correct config.

* feat: add scaleway security_group_rule management (ansible#45694)

* feat: add scaleway security_group_rule management

* homebrew_cask: Fixes ansible#38772

* Fix typo in ec2_vpnc_nat_gateway module (ansible#46304)

- Added space between `format` and `in` on return item `create_time`

* Add new member to botmeta

* Add label pure_storage for all related files. Add team_purestorage macro

* Add logstash_plugin example for lower heap size

In a scenario where you've set your logstash heap size high, you may need to set your heap lower in order to execute logstash-plugin while logstash is still running.

Here's an example of someone running into insufficient memory while executing logstash-plugin: https://discuss.elastic.co/t/logstash-plugin-and-jvm-options/99646

This scenario is probably fairly common, so it may be worth documenting as an example.

+label: docsite_pr

* Fix callout json plugin show global stats (ansible#43123)

* fix callback Plugin json to support global stat set by set_stats module

* refactor to not break compatiblity, add trailing comma on output dict

* Remove sorted, as it not needed

* refactor, to sivels better code

* clean some code messup

* add changelog fragment

* added missing new line

* fix pep8 stuff

* Mention YAML as a AWS CloudFormation template language (ansible#46345)

* avoid tests when ncclient is not installed

* Add configuration to override location of ansible-connection (ansible#46128)

* Add configuration to override location of ansible-connection

* Check var or argv[0] before $PATH

* Add the k8s label to the k8s files

k8s label for inventory plugin, module_utils
and modules

* WIP: Check that union Jinja filter can be chained (ansible#46298)

* Check that union Jinja filter can be chained

* set filters: fix unexpected templating type error

this error occurs with Jinja 2.10 since 32ec69d,
for example when union filters are chained:

$ ansible all -i localhost, -mdebug -a"msg={{ []|union([])|union([]) }}"
localhost | FAILED! => {
    "msg": "Unexpected templating type error occurred on ({{ []|union([])|union([]) }}):
            unsupported operand type(s) for +: 'set' and 'list'"
}

* Use specified loopvar in include_role example loop

* clean up doc - removed required: false (ansible#46357)

* remove comments from multiplle yaml string that breaks tests for now

* Use recursive_diff for kubernetes (ansible#45645)

Move recursive_diff from cloudfront_distribution to
common.dict_transformations and reuse it in k8s modules

* New module: routeros_facts – collect facts from RouterOS devices (ansible#46114)

* feat(routeros): implement routeros_facts module

* fix(routeros): review by felixfontein

* fix(routeros): review by ganeshrn

* fix(routeros): review by felixfontein

* vcenter_folder - fix error events being generated, incorrect parent folders (ansible#45951)

* fix error events being generated when vmware folders exist
* fix incorrect parent folders being identified (wrong type)

* Ignore empty result of rabbitmqctl list_user_permissions (ansible#35598)

Fix ansible#34863

* Fix typo in the author's github username.

Ansibot is looking at the author's github username to query reviews for
modules in the same namespace.

* Correct invalid example in jenkins_script docs (ansible#46193)

* Add ssl support to consul_kv lookup (ansible#42456)

* implemented lookup_consul_kv
* added missing version_added for consul_url ini section
* added default value for ANSIBLE_CONSUL_CLIENT_CERT and added some more documentation
* removed trailing whitespaces
* fixed indention
* Fixes in Documentation
* removed trailing whitespace
* removed trailing whitespace

* Add examples for bind and unmount to mount module docs

PR ansible#46375

* Updates release & maintenance version docs for 2.7

* Rebalance shippable/posix/ CI groups.

* disable gather facts and update playbook output (ansible#46409)

* disable facts gather and update playbook output

* fix output

* Move network utils that are used by AWS modules (ansible#45579)

* Separate networking tools that may be used by modules outside of networking so changes to networking-only utilities don't trigger AWS integration tests

* Add unit tests for moved network utils

* Add comment to prevent imports from being mistakenly removed

* Move to_bits as well

* New option JUNIT_TASK_RELATIVE_PATH to output relative paths. (ansible#37274)

* New option JUNIT_TASK_RELATIVE_PATH to output relative paths.

It makes the output in Jenkins much more readable as the absolute
path was taking the whole width of the screen, leaving no space for
the actual message.

A makedirs instead of mkdir slipped in as to make the creation of
the output directory recursive, hope this is OK.

* Add version_added field to doc set to 2.8

* Fix ansible-test multi-group smoke test handling. (ansible#46363)

* Fix ansible-test smoke tests across groups.
* Fix ansible-test list arg defaults.
* Fix ansible-test require and exclude delegation.
* Fix detection of Windows specific changes.
* Add minimal Windows testing for Python 3.7.

* Fix ansible-test encoding issues for exceptions.

* Docs: Clean up of 'blockinfile' module docs (ansible#46331)

* Docs: Clean up of 'blockinfile' module docs

This is part of a series of module doc cleanups.

* A few more fixes after review

* win_exec: refactor PS exec runner (ansible#45334)

* win_exec: refactor PS exec runner

* more changes for PSCore compatibility

* made some changes based on the recent review

* split up module exec scripts for smaller payload

* removed C# module support to focus on just error msg improvement

* cleaned up c# test classifier code

* Change with_*: loops to loop: loops. Fix some examples. (ansible#46373)

* VMware: Add check mode support in vmware_host_config_facts (ansible#46272)

* Only delete key from redis in-memory cache if present (ansible#35126)

Fixes ansible#35120 : the redis cache plugin keeps key/value
entries in an in-memory cache to avoid hitting the
redis database each time.

The problem is that a cache entry is only set when
a value is get or set but it is always deleted when
trying to delete a value.

When the --flush-cache ansible-playbook option is used,
the redis cache plugin is first asked to remove every
entry corresponding to every hostname present in the inventory.
As no value as been set/get so far, it then tries to delete
an unexisting value from the cache and hence crashes with
a KeyError exception.

* Docsite: Add a new tool:  Ansible Playbook Grapher (ansible#46435)

Add Ansible Playbook Grapher: a tool create a graph representing your Ansible playbook tasks and roles.

https://github.com/haidaraM/ansible-playbook-grapher

+label: docsite_pr

* fixed tests after EAP set to Stop globally, ci_complete

* Docs: Cleanup selinux_permissive module docs (ansible#46351)

Update the selinux_permissive instructions and add a comment to the
provided example.

Signed-off-by: Major Hayden <major@redhat.com>

* Macports: Add upgrade parameter and replace update_ports with selfupdate (ansible#45049)

* macports: Replace update_ports with selfupdate

- Macports discourages use of `port sync` and recommends using `port
selfupdate` instead.
- Keep `update_cache` and `update_ports` as aliases.
- No longer require the `name` parameter so that `selfupdate` can be
used in a task by itself.

* macports: Add upgrade parameter

- New upgrade parameter which can be used to upgrade all outdated ports.

* Add changelog fragment

* Update asa_config.py (ansible#46448)

<!--- Your description here -->

+label: docsite_pr

* Docs: Clean up of 'file' module docs (ansible#46327)

This is part of a series of module doc cleanups.

* Use default-test-container version 1.3.0.

* Docs: iptables module cleanup (ansible#46368)

Signed-off-by: Major Hayden <major@redhat.com>

* Subscribing to notifications. (ansible#46372)

* win_chocolatey: remove test packages after tests are run (ansible#46431)

* ps-lint: ignore rules that are not relevant to Ansible (ansible#46376)

* Docs: Clean up of 'assemble' module docs (ansible#46328)

This is part of a series of module doc cleanups.

* Docs: Cleanup make module docs (ansible#46422)

Signed-off-by: Major Hayden <major@redhat.com>

* Use proper index value with insertbefore on a one line file (ansible#46071)

Add tests and changelog

* Add file exists check in integration-aliases test.

* remove unnecessary space (ansible#46462)

kindly advised from jborean93

* Docs: Clean up 'win_service' module docs (ansible#46407)

* Docs: Clean up 'win_service' module docs

This is part of a series of module doc cleanups.

* Fix typo pause vs paused

* Use both YAML list syntaxes

* Lookup plugin for rabbitmq (ansible#44070)

* Adding a basic get lookup for rabbitmq.

* Always return a list

* If content type is JSON, make accessible via dict.

* Fixed incorrect json.loads variable and missing raise

* Change to document returned data

* Fixed pep8 issues

* Adding integration testing

* Moving lookup intgration tests to new target

* New rabbitmq lookup plugin (ansible#44070).

* New rabbitmq lookup plugin (ansible#44070).

* PR review feedback updates

* Testing pika is installed

* Minor mods to tests

* Check if connection is already closed or closing

* Updated tests and connection testing

* PR review feedback updates

* PR review include ValueError in AnsibleError output

* Suggesting to use set_fact when using returned variable more than once.

* Cleaned up some tests, added some notes and handling connection closure on some exceptions.

* Removed finally statement and added some additional error handling.

* Added some additional error handling.

* PR review updates.

* Additional integration tests and removing return in finally

* Updated version

* Changing back to running tests on ubuntu.

* Additional tests

* Running tests on  Ubuntu only

* Fixing syntax error

* Fixing ingtegration tests and a string/byte issue

* Removed non-required test and fixed BOTMETA

* Trying to fix integration test failure on ubuntu1404

* Some issues occured when handling messages from the queue with to_native.  Switching to to_text resolved the issues.

* Renaming channel to queue (thanks dch). Disabling trusty tests.

* Fix spelling error in subelements Filter example (ansible#46446)

<!--- Your description here -->

+label: docsite_pr

* updates latest in docs conf.py (ansible#46400)

* Docs: Clean up of 'template' module docs (ansible#46297)

* Docs: Clean up of 'template' module docs

* Changed influenced by review comments

* add simple j2 example to vyos_config (ansible#46442)

* Docs: Clean up 'win_reboot' module docs (ansible#46377)

* Docs: Clean up 'win_reboot' module docs

This is part of a series of module doc cleanups.

* Remove hypothetical example

* Docs: Clean up of 'fetch' module docs (ansible#46330)

* Docs: Clean up of 'fetch' module docs

This is part of a series of module doc cleanups.

* Fixes as suggested by review

* Make default_operation optional in netconf_config module (ansible#46333)

Fixes ansible#46257

*  As per netconf rfc default-operation value is optional,
   hence removing the default value for default_operation
   option.

* Improve ansible-test environment checking between tests. (ansible#46459)

* Add unified diff output to environment validation.

This makes it easier to see where the environment changed.

* Compare Python interpreters by version to pip shebangs.

This helps expose cases where pip executables use a different
Python interpreter than is expected.

* Query `pip.__version__` instead of using `pip --version`.

This is a much faster way to query the pip version. It also more
closely matches how we invoke pip within ansible-test.

* Remove redundant environment scan between tests.

This reuses the environment scan from the end of the previous test
as the basis for comparison during the next test.

* VMware: Add check mode support to module vmware_host_acceptance (ansible#46260)

* Improve module description
* Add check mode support

* VMware: Add check mode support to module vmware_host_firewall_facts (ansible#46265)

evandam added a commit to evandam/ansible that referenced this issue Jan 16, 2019

ewarnke added a commit to ewarnke/ansible that referenced this issue Mar 20, 2019

Update lib/ansible/modules/files/file.py
Doc language ansible#2

Co-Authored-By: ewarnke <32573149+ewarnke@users.noreply.github.com>

chrisvanheuveln referenced this issue in chrisvanheuveln/ansible Mar 22, 2019

trishnaguha added a commit that referenced this issue Mar 27, 2019

nxos_interfaces_ospf: fix passive-interface states & check_mode (#54260)
* nxos_interfaces_ospf: fix passive-interface states & check_mode

This fix addresses issues #41704 and #45343.

The crux of the problem is that `passive-interface` should have been treated as a tri-state value instead of a boolean.

The `no` form of the command disables the passive state on an interface (allows it to form adjacencies and send routing updates).  It's essentially an override for `passive-interface default` which enables passive state on all OSPF interfaces.\*
This `no` config will be present in `running-config`.

   \**See `router ospf` configuration.*

Since both enable and disable states are explicit configs, the proper way to remove either of these is with the `default` syntax.

Passive-interface config syntax:
```
  ip ospf passive-interface              # enable  (nvgens)
  no ip ospf passive-interface           # disable (nvgens)
  default ip ospf passive-interface      # default (removes config, does not nvgen)
```

Code changes:

* `passive_interface` param changed from boolean to string, restricted to `true`,`false`,`default`.

* Several passive-interface specific checks were added because the existing module logic tends to test for true or false and doesn't handle the None case.

* Fixed `check_mode`.

Sanity verified on: N9K,N7K,N3K,N6K

* Fix doc header

* Unit tests for passive-interface

* doc fix #2

* Fix indent for SA

* Remove 'default' keyword, restore bool behavior

* remove changes to sanity

trishnaguha added a commit to trishnaguha/ansible that referenced this issue Apr 1, 2019

nxos_interfaces_ospf: fix passive-interface states & check_mode (ansi…
…ble#54260)

* nxos_interfaces_ospf: fix passive-interface states & check_mode

This fix addresses issues ansible#41704 and ansible#45343.

The crux of the problem is that `passive-interface` should have been treated as a tri-state value instead of a boolean.

The `no` form of the command disables the passive state on an interface (allows it to form adjacencies and send routing updates).  It's essentially an override for `passive-interface default` which enables passive state on all OSPF interfaces.\*
This `no` config will be present in `running-config`.

   \**See `router ospf` configuration.*

Since both enable and disable states are explicit configs, the proper way to remove either of these is with the `default` syntax.

Passive-interface config syntax:
```
  ip ospf passive-interface              # enable  (nvgens)
  no ip ospf passive-interface           # disable (nvgens)
  default ip ospf passive-interface      # default (removes config, does not nvgen)
```

Code changes:

* `passive_interface` param changed from boolean to string, restricted to `true`,`false`,`default`.

* Several passive-interface specific checks were added because the existing module logic tends to test for true or false and doesn't handle the None case.

* Fixed `check_mode`.

Sanity verified on: N9K,N7K,N3K,N6K

* Fix doc header

* Unit tests for passive-interface

* doc fix ansible#2

* Fix indent for SA

* Remove 'default' keyword, restore bool behavior

* remove changes to sanity

(cherry picked from commit 20fb77c)

abadger added a commit that referenced this issue Apr 4, 2019

nxos_interfaces_ospf: fix passive-interface states & check_mode (#54260)
* nxos_interfaces_ospf: fix passive-interface states & check_mode

This fix addresses issues #41704 and #45343.

The crux of the problem is that `passive-interface` should have been treated as a tri-state value instead of a boolean.

The `no` form of the command disables the passive state on an interface (allows it to form adjacencies and send routing updates).  It's essentially an override for `passive-interface default` which enables passive state on all OSPF interfaces.\*
This `no` config will be present in `running-config`.

   \**See `router ospf` configuration.*

Since both enable and disable states are explicit configs, the proper way to remove either of these is with the `default` syntax.

Passive-interface config syntax:
```
  ip ospf passive-interface              # enable  (nvgens)
  no ip ospf passive-interface           # disable (nvgens)
  default ip ospf passive-interface      # default (removes config, does not nvgen)
```

Code changes:

* `passive_interface` param changed from boolean to string, restricted to `true`,`false`,`default`.

* Several passive-interface specific checks were added because the existing module logic tends to test for true or false and doesn't handle the None case.

* Fixed `check_mode`.

Sanity verified on: N9K,N7K,N3K,N6K

* Fix doc header

* Unit tests for passive-interface

* doc fix #2

* Fix indent for SA

* Remove 'default' keyword, restore bool behavior

* remove changes to sanity

(cherry picked from commit 20fb77c)

syncpak pushed a commit to syncpak/ansible that referenced this issue Apr 10, 2019

syncpak pushed a commit to syncpak/ansible that referenced this issue Apr 10, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.