| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#75452)
Rather than adding further complexity to the regex, preprocess the output to
remove any empty lines. Now the only purpose of the regex is to fix
wrapped lines.
Fixes #70949
(cherry picked from commit 51f2f1ac5ee1416f097587ff81b721b3ccc36971)
Co-authored-by: Martin Krizek <martin.krizek@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
(cherry picked from commit a3cc6a581ef191faf1c9ec102d1c116c4c2a8778)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes a bug which under certain conditions results in data
returned from lookups not being marked as unsafe.
Each time Templar.do_template is invoked a new AnsibleContext is
created and stored effectively at two places:
1) as an instance variable in templar_obj.cur_context
2) as a local variable called new_context in do_template method of Templar
Due to custom functionality in Ansible's Context that allows for nested
templating it is possible that during resolving variable's value
template/do_template method is called recursively again, again creating
a new context. At that point the problem manifests itself because as
mentioned in 1) above the context is overwriten on the templar object
which means that any subsequent calls to _lookup will use the new
context to mark it as unsafe which is now different to the local
new_context which is used for testing for unsafe property.
The solution to the problem appears to be to restore the original
context inside do_template and also to eliminate the local variable
new_context to prevent problems in the future.
It appears that we don't have a better way of storing the context other
than as some form of global variable and so this appears to be the
"best" solution possible at this point. Hopefully data tagging will be
the solution here.
For more examples see unit and integration tests included in this patch.
Fixes #77535
(cherry picked from commit 3980eb8c09d170a861351f8aff4a1aa1a8cbb626)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(#77347)
(cherry picked from commit ff184b0815cdbf7dc222fd9d7b0cfaa93d5fe03c)
|
|
|
|
|
|
|
|
|
| |
* winrm - ensure callers PATH for kinit is set
* Fix unit test expectations
* Fix type annotation
(cherry picked from commit 60b4200bc6fee69384da990bb7884f58577fc724)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* use same timeout for galaxy api interactions (#77088)
Also, bump the default. A number of people have reported problems with
this 20 second timeout for a couple of years on
https://github.com/ansible/galaxy/issues/2302
It is mentioned in the issue that resolving dns can sometimes take up to
30 seconds, and that this timeout includes dns resolution.
Includes a changelog message
* fix type hint
Co-authored-by: Matt Clay <matt@mystile.com>
Co-authored-by: Matt Davis <6775756+nitzmahone@users.noreply.github.com>
Co-authored-by: Matt Clay <matt@mystile.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix collection redirects for filter and test plugins (#77210)
* Fix collection redirects for jinja2 filters/tests
* Handle recursive redirects
Co-authored-by: Matt Martz <matt@sivel.net>
(cherry picked from commit 8063643b4cec51a72377da5f3fa354d3ff9e737a)
* The error message is only capitalized on 2.13. Make test more flexible.
(cherry picked from commit 734777ef05b8c200f45336a8b9b41f9f9af597c1)
|
|
|
|
|
|
|
|
|
|
|
| |
modified content (#77129)
* Fix 'ansible-galaxy collection verify' to report files/directories not listed in the FILES.json
(cherry picked from commit a1d467dbb21e00cdb0ed38baf0e43e583185dc59)
* changelog
(cherry picked from commit 3d49d6f69ec1afa2234a21a1f9cd273d55cb6597)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#77126)
* [stable-2.11] Use full python package for ansiballz cache filenames (#77090)
* Use full python package for ansiballz cache filenames
* Be a little more explicit about test goals
(cherry picked from commit 8cbe143)
Co-authored-by: Matt Martz <matt@sivel.net>
* linting
|
| |
|
| |
|
| |
|
|
|
| |
Signed-off-by: Christian M. Adams <chadams@redhat.com>
|
|
|
|
|
|
|
|
|
| |
ssh plugin, use 'correct' information source in all cases
* still fallback to pc
* added inventory to new test
* undef var can still show as parser error on pc
now task_exectuer has a more accurate error handling
(cherry picked from commit be19863e44cc6b78706147b25489a73d7c8fbcb5)
|
|
|
|
|
|
| |
needed to properly propagate some arguments by convention: subset, filter
Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com>
(cherry picked from commit 5bddecb048aae0a7fc84e38e086ac90445c4edb4)
|
|
|
|
|
|
|
| |
* updated tests to conform to new block inheritance
Co-authored-by: Brian Scholer <1260690+briantist@users.noreply.github.com>
Co-authored-by: Sloane Hertel <19572925+s-hertel@users.noreply.github.com>
(cherry picked from commit b1d6750e8bbdf507a4af24a4319b78b7287e233c)
|
|
|
| |
(cherry picked from commit 47faa6e206ccd697b4050062147a5d3242435597)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [stable-2.11] ansible-test - Use relative paths in junit output. (#76871)
* ansible-test - Use relative paths in junit output.
* ansible-test - Handle out-of-tree JUnit paths.
* Also fix a traceback in the junit callback during automatic fact gathering.
(cherry picked from commit fbb5d56bd274c44b193cb95f0230b9352f62aab2)
* Fix task path unicode error in junit callback.
(cherry picked from commit 41db6d8d35900d425df3228406db3fec61ab2269)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* service_facts, now more accurate on systemd
(cherry picked from commit 82bab063e7c60b77596c5c87258d5c3398b5efc2)
|
| |
|
|
|
|
|
|
|
| |
(#76797)
(cherry picked from commit 29bdb8b)
Co-authored-by: Matt Martz <matt@sivel.net>
|
|
|
|
|
|
|
|
|
|
| |
* include_vars initialize failed
if source dir is given, but not present and traversal is empty you
can end up trying to access failed w/o it ever being defined.
also future proof for more corner cases in decision tree
(cherry picked from commit 89c884e2a2bd124b49bf9419f053f659a7d1c554)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* ssh connection avoid parsiing own debug (#76732)
- Avoids false positives on become strings being echoed back
by ssh cli itself
- added test for debug lines
- also simplified some of existing test code
(cherry picked from commit 0ff80a15ba40c2aff3b96c1152f19c97a92d3c97)
* unicoode
* dont make em ascii
|
|
|
|
|
|
| |
* handle 'fun' control paths by quoting the option when passed to ssh cli
Co-authored-by: Matt Clay <matt@mystile.com>
(cherry picked from commit aa022dba2d141cbd3b862767400ba4f714a9edd1)
|
|
|
|
|
|
|
|
|
| |
* Use correct markup in documentation (#76545)
(cherry picked from commit 9d1898b1ef8a84f53c1a5f243744071b3aee1e42)
* Fix markup.
(cherry picked from commit c24c4790610c5bb244b689b1cfd69f25c18e4ddd)
|
|
|
| |
(cherry picked from commit 8482ee4e9a992abe998c7f885ef5e873f9ef5894)
|
|
|
|
|
|
|
|
|
|
| |
When we introduced an include parameter to the unarchive module, we
inadvertenly flipped the exclusion logic. This flip meant that the
unarchive module started rejecting files that should be extracted.
This commit flips the bad logic and adds some tests that will make
sure things do not go bad again.
(cherry picked from commit f92830d16e2fcca394a69b13e1017350e07152a3)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
False and None) (#75168) (#76206)
* set host_key_checking check to False, rather than if not (which captures False and None)
* add host_key_checking default to ssh.py / update documentation
(cherry picked from commit d527be8a524ff0f6bd23dfc48c6b511b9d14ddf8)
Co-authored-by: James Spurin <james@spurin.com>
|
|
|
| |
(cherry picked from commit db2aee558bd58269b380c6643fb87bee2c00ee47)
|
|
|
|
|
|
|
|
|
| |
(#76189)
* Skip recursive suboption validation if sub_parameters is not a dictionary
* Ensure sub parameter elements is a sequence to prevent iterating over string characters and causing duplicate error messages for the same param
(cherry picked from commit b5ed41edb34a387c560e172ee2928cc8ac9b4959)
|