You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* In the `nxos_igmp_interface` module, `oif_prefix` and `oif_source` properties are deprecated.
14
14
Use the `oif_ps` parameter with a dictionary of prefix and source to values instead.
15
15
16
-
See [Porting Guide](http://docs.ansible.com/ansible/devel/porting_guides/porting_guides.html) for more information
16
+
See [Porting Guide](https://docs.ansible.com/ansible/devel/porting_guides/porting_guides.html) for more information
17
17
18
18
### Minor Changes
19
19
* Removed restriction from protocol in cloudflare_dns module to allow other protocols than tcp and udp to be specified.
@@ -127,7 +127,7 @@ See [Porting Guide](https://docs.ansible.com/ansible/devel/porting_guides/portin
127
127
* network_cli
128
128
* netconf
129
129
130
-
While neither is technically a new plugin, these connections may now be used directly with network modules. See [Network Best Practices for Ansible 2.5](http://docs.ansible.com/ansible/devel/network_best_practices_2.5.html) for more details.
130
+
While neither is technically a new plugin, these connections may now be used directly with network modules. See [Network Best Practices for Ansible 2.5](https://docs.ansible.com/ansible/devel/network_best_practices_2.5.html) for more details.
131
131
132
132
#### Filters
133
133
* parse_xml
@@ -1358,7 +1358,7 @@ While neither is technically a new plugin, these connections may now be used dir
1358
1358
1359
1359
## 2.3 "Ramble On" - 2017-04-12
1360
1360
1361
-
Moving to Ansible 2.3 guide http://docs.ansible.com/ansible/porting_guide_2.3.html
1361
+
Moving to Ansible 2.3 guide https://docs.ansible.com/ansible/porting_guide_2.3.html
1362
1362
1363
1363
### Major Changes
1364
1364
* Documented and renamed the previously released 'single var vaulting' feature, allowing user to use vault encryption for single variables in a normal YAML vars file.
@@ -2133,7 +2133,7 @@ Module fixes:
2133
2133
* Added a new strategy `debug`, which allows per-task debugging of playbooks, for more details see https://docs.ansible.com/ansible/playbooks_debugger.html
2134
2134
* Added a new option for tasks: `loop_control`. This currently only supports one option - `loop_var`, which allows a different loop variable from `item` to be used.
2135
2135
* Added the ability to filter facts returned by the fact gathering setup step using the `gather_subset` option on the play or in the ansible.cfg configuration file.
2136
-
See http://docs.ansible.com/ansible/intro_configuration.html#gathering for details on the format of the option.
2136
+
See https://docs.ansible.com/ansible/intro_configuration.html#gathering for details on the format of the option.
2137
2137
* Added the ability to send per-item callbacks, rather than a batch update (this more closely resembles the behavior of Ansible 1.x).
2138
2138
* Added facility for modules to send back 'diff' for display when ansible is called with --diff, updated several modules to return this info
2139
2139
* Added ansible-console tool, a REPL shell that allows running adhoc tasks against a chosen inventory (based on https://github.com/dominis/ansible-shell)
Copy file name to clipboardExpand all lines: CODING_GUIDELINES.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ PEP 8 and basic style checks
20
20
*[PEP 8](https://www.python.org/dev/peps/pep-0008/) is a great Python style guide, which you should read.
21
21
* PEP 8 must not be strictly followed in all aspects, but most of it is good advice.
22
22
* The line is limited to 160 characters.
23
-
* To run checks for things we care about, use [ansible-test](http://docs.ansible.com/ansible/dev_guide/testing_pep8.html#running-locally).
23
+
* To run checks for things we care about, use [ansible-test](https://docs.ansible.com/ansible/dev_guide/testing_pep8.html#running-locally).
24
24
* Similarly, additional checks can be made with "make pyflakes".
25
25
* There is no need to submit code changes for PEP 8 and pyflakes fixes, as these break attribution history. Project leadership will make these periodically.
26
26
* Do not submit pull requests that simply adjust whitespace in the code.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -5,19 +5,19 @@ Hi! Nice to see you here!
5
5
6
6
## QUESTIONS ?
7
7
8
-
Please see the [community guide](http://docs.ansible.com/ansible/latest/community/index.html) for information on how to ask questions on the [mailing lists](http://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information) and IRC.
8
+
Please see the [community guide](https://docs.ansible.com/ansible/latest/community/index.html) for information on how to ask questions on the [mailing lists](https://docs.ansible.com/ansible/latest/community/communication.html#mailing-list-information) and IRC.
9
9
10
10
The GitHub issue tracker is not the best place for questions for various reasons, but both IRC and the mailing list are very helpful places for those things, as the community page explains best.
11
11
12
12
13
13
## CONTRIBUTING ?
14
14
15
-
Please see the [community guide](http://docs.ansible.com/ansible/latest/community/index.html) for information regarding the contribution process. Important license agreement information is also included on that page.
15
+
Please see the [community guide](https://docs.ansible.com/ansible/latest/community/index.html) for information regarding the contribution process. Important license agreement information is also included on that page.
16
16
17
17
18
18
## BUG TO REPORT ?
19
19
20
-
First and foremost, also check the [community guide](http://docs.ansible.com/ansible/latest/community/index.html).
20
+
First and foremost, also check the [community guide](https://docs.ansible.com/ansible/latest/community/index.html).
21
21
22
22
You can report bugs or make enhancement requests at the [Ansible GitHub issue page](https://github.com/ansible/ansible/issues/new) by filling out the issue template that will be presented.
The Ansible Module Maintainer Guidelines can now be found in the [official Ansible community guide](http://docs.ansible.com/ansible/latest/community/maintainers.html).
3
+
The Ansible Module Maintainer Guidelines can now be found in the [official Ansible community guide](https://docs.ansible.com/ansible/latest/community/maintainers.html).
Copy file name to clipboardExpand all lines: docs/docsite/README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
Homepage and documentation source for Ansible
2
2
=============================================
3
3
4
-
This project hosts the source behind [docs.ansible.com](http://docs.ansible.com/)
4
+
This project hosts the source behind [docs.ansible.com](https://docs.ansible.com/)
5
5
6
6
Contributions to the documentation are welcome. To make changes, submit a pull request that changes the reStructuredText files in the `rst/` directory only, and the core team can do a docs build and push the static files.
7
7
@@ -18,4 +18,4 @@ Note that module documentation can actually be [generated from a DOCUMENTATION d
18
18
To install sphinx and the required theme, install pip and then "pip install sphinx sphinx_rtd_theme"
Copy file name to clipboardExpand all lines: docs/docsite/rst/installation_guide/intro_installation.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -277,7 +277,7 @@ Readers that use virtualenv can also install Ansible under virtualenv, though we
277
277
Tarballs of Tagged Releases
278
278
+++++++++++++++++++++++++++
279
279
280
-
Packaging Ansible or wanting to build a local package yourself, but don't want to do a git checkout? Tarballs of releases are available on the `Ansible downloads <http://releases.ansible.com/ansible>`_ page.
280
+
Packaging Ansible or wanting to build a local package yourself, but don't want to do a git checkout? Tarballs of releases are available on the `Ansible downloads <https://releases.ansible.com/ansible>`_ page.
281
281
282
282
These releases are also tagged in the `git repository <https://github.com/ansible/ansible/releases>`_ with the release version.
Copy file name to clipboardExpand all lines: docs/docsite/rst/scenario_guides/guide_aci.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ For instance ensuring that a specific tenant exists, is done using the following
65
65
description: Customer XYZ
66
66
state: present
67
67
68
-
A complete list of existing ACI modules is available for the latest stable release on the :ref:`list of network modules <list_of_network_modules>`. You can also view the `current development version <http://docs.ansible.com/ansible/devel/modules/list_of_network_modules.html#aci>`_.
68
+
A complete list of existing ACI modules is available for the latest stable release on the :ref:`list of network modules <list_of_network_modules>`. You can also view the `current development version <https://docs.ansible.com/ansible/devel/modules/list_of_network_modules.html#aci>`_.
### Common Documentation Fragments for Connection Parameters
160
160
161
-
There are two [common documentation fragments](http://docs.ansible.com/ansible/latest/dev_guide/developing_modules_documenting.html#documentation-fragments)
161
+
There are two [common documentation fragments](https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_documenting.html#documentation-fragments)
162
162
that should be included into almost all AWS modules:
163
163
164
164
*`aws` - contains the common boto connection parameters
@@ -518,8 +518,8 @@ affect the module are detected. At a minimum this should cover the key API calls
518
518
documented return values are present in the module result.
519
519
520
520
For general information on running the integration tests see the [Integration Tests page of the
521
-
Module Development Guide](http://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html).
522
-
Particularly the [cloud test configuration section](http://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html#other-configuration-for-cloud-tests)
521
+
Module Development Guide](https://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html).
522
+
Particularly the [cloud test configuration section](https://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html#other-configuration-for-cloud-tests)
523
523
524
524
The integration tests for your module should be added in `test/integration/targets/MODULE_NAME`.
525
525
@@ -567,7 +567,7 @@ for every call, it's preferrable to use [YAML Anchors](http://blog.daemonl.com/2
567
567
568
568
### AWS Permissions for Integration Tests
569
569
570
-
As explained in the [Integration Test guide](http://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html#iam-policies-for-aws)
570
+
As explained in the [Integration Test guide](https://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html#iam-policies-for-aws)
571
571
there are defined IAM policies in `hacking/aws_config/testing_policies/` that contain the necessary permissions
0 commit comments