Skip to content
Branch: devel
Commits on Jun 28, 2017
  1. letsencrypt: FIX CN parsing to work with OpenSSL 1.1 (#25935)

    hsoft authored and resmo committed Jun 28, 2017
    As we can see in
    CN used to be without whitespaces around the `=` but OpenSSL 1.1 introduced
    1.0.1: subject=/
    1.1.0: subject=CN =
    This commit makes them optional.
    OpenSSL 1.1 is present on the newly-released Debian Stretch, so absence
    of this fix makes us not being able to use this module on this distro.
Commits on Dec 8, 2016
  1. unarchive: use Python's tarfile module for tar listing (#3575)

    hsoft authored and mattclay committed May 2, 2016
    * unarchive: use Python's tarfile module for tar listing
    fixes #11348
    Depending on the current active locale, `tar`'s file listing can end up
    spitting backslash-escaped characters. Unfortunately, when that happens,
    we end up with double-escaped backslashes, giving us a wrong path,
    making our action fail.
    We could try un-double-escaping our paths, but that would be complicated
    and, I think, error-prone. The easiest way forward seemed to simply use
    the `tarfile` module.
    Why use it only for listing? Because the `unarchive` option also
    supports the `extra_opts` option, and that supporting this would require
    us to mimick `tar`'s interface.
    For listing files, however, I don't think that the loss of `extra_opts`
    support causes problems (well, I hope so).
    * unarchive: re-add xz decompression support
    Following previous change to use Python's `tarfile` module for tar file
    listing, we lost `xz` decompression support. This commits re-add it by
    adding a special case in `TarXzArchive` that pre-decompresses the source
Commits on Nov 29, 2016
  1. Fix regression in jinja2 include search path (#18617)

    hsoft authored and bcoca committed Nov 29, 2016
    * Fix regression in jinja2 include search path
    Since commit 3c39bb5, the 'ansible_search_path' variable is used to set
    jinja2's search path for {% include %} directives. However, this path is
    the the proper one because our templates live in 'templates' subdirs in
    our search path.
    This is a regression because previously, our include search path would
    include the dirname of the currently interpreted file, which worked most
    of the time.
    fixes #18526
    * Fix template lookup search path
    Improve fix in commit c96c853 so that the search path contain both
    template-suffixed paths as well as original paths.
    ref PR #18617
    * Add integration test for template lookups
    Tests regression at #18526
    This test fails on current devel branch and succeeds on PR #18617
You can’t perform that action at this time.