[ansible-devel] Ansible-5.0.0 alpha1 ready for testing

Hi all, We're happy to announce that the Ansible 5.0.0 alpha1 package is now available! This update is based on the ansible-core-2.12.x package which is a major update from the one used by Ansible 4. Ansible 4 was based on Ansible Core 2.11.x. There may be backwards incompatibilities in the core

[ansible-devel] Ansible-4.6.0 release

Hi all, We're happy to announce that the ansible-4.6.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need t

[ansible-devel] Ansible-4.5.0 has been released

Hi all, We're happy to announce that the ansible-4.5.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need t

[ansible-devel] Ansible-4.4.0 released

Hi all, We're happy to announce that the ansible-4.4.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need t

[ansible-devel] Ansible-4.3.0 has been released

Hi all, We're happy to announce that the ansible-4.3.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need t

[ansible-devel] Ansible 4.2.0 released

Hi all, We're happy to announce that the ansible-4.2.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need t

[ansible-devel] Ansible-4.1.0 release

Hi all, We're happy to announce that the ansible-4.1.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. How to get it - Due to a limitation in pip, if you are upgrading from Ansible 3 (or earlier), you need t

[ansible-devel] Ansible 4.0.0 final has been released!

log/ansible-3.0.0-qa Porting Help - A unified porting guide for collections which have opted-in is available here: https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "An

[ansible-devel] Ansible-3.4.0 released

Hi all, We're happy to announce that the ansible-3.4.0 package has been released! The update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the backgro

[ansible-devel] Ansible-4.0.0rc1

Hi all, We're happy to announce that the Ansible-4.0.0 release candidate 1 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible 3 package (Ansible 3 was based on Ansible-base-2.10.x). There may be backwards incompatibilities in

[ansible-devel] Ansible-4.0.0 beta2 released

Hi all, We're happy to announce that the Ansible-4.0.0 beta2 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible-3 package (Ansible-3 was based on Ansible-base-2.10.x). There may be backwards incompatibilities in the core playb

[ansible-devel] FYI: Reminder about ansible 3 & 4 release dates

Just a brief reminder about the Ansible 3 and 4 schedule: * The last Ansible 3 release is planned for May 11, 2021 * Ansible 4.0.0 release candidate 1 is also planned for May 11, 2021 * If there are no blocker bugs discovered, Ansible 4.0.0 final will be made on May 18, 2021 -Toshio -- You rece

[ansible-devel] Ansible 4.0.0 beta1 release

Hi all, We're happy to announce that the Ansible-4.0.0 beta1 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible-3 package (Ansible-3 was based on Ansible-base-2.10.x). There may be backwards incompatibilities in the core playb

[ansible-devel] Ansible3.3.0

Hi all, We're happy to announce that the ansible-3.3.0 package was released on April 20! The update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the

[ansible-devel] Ansible 4.0.0 alpha4 released

Hi all, We're happy to announce that the Ansible-4.0.0 alpha4 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible-3 package (Ansible-3 was based on Ansible-base-2.10.x). There may be backwards incompatibilities in the core play

[ansible-devel] Ansible-4.0.0 alpha 3

Hi all, We're happy to announce that the Ansible-4.0.0 alpha3 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible-3 package (Ansible-3 was based on Ansible-base-2.10.x). There may be backwards incompatibilities in the core play

[ansible-devel] Ansible-3.2.0 released

Hi all, We're happy to announce that the ansible-3.2.0 package is now available! This update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the backgro

[ansible-devel] ansible-4.0.0 alpha2

Hi all, We're happy to announce that the Ansible-4.0.0 alpha2 package is now available! This update is based on the Ansible-core-2.11.x package which is a major update from the Ansible-3 package (Ansible-3 was based on Ansible-core-2.10.x). There may be backwards incompatibilities in the core play

[ansible-devel] Ansible-4.0.0 alpha1 released!

eenode.net Porting Help - A unified porting guide for collections which have opted-in is being worked on. For now, you can find it in this pull request: https://github.com/ansible/ansible/pull/73930 -Toshio Kuratomi P.S. Many thanks to felixfontein for doing most of the work to up

[ansible-devel] Ansible-3.1.0 release and ansible-4.0 alpha1 delay

Hi all, We're happy to announce that the ansible-3.1.0 package is now available! This update contains bugfixes and new, backwards compatible features in the contained collections. If you would like to learn about how and why we got to version 3.0.0, we invite you to visit our blog for the backgro

[ansible-devel] Ansible-3.0.0 released

Hi all, We're happy to announce that the ansible-3.0.0 package is now available! This update is based on the ansible-base-2.10.x package just like ansible-2.10 was so the changes shouldn't be too major. However, it does contain new major versions of many collections which means that there will be

[ansible-devel] Re: Ansible-3.0.0 release candidate 1

ra days so at yesterday's Community IRC meeting we voted to allow a slip to Thursday, February, 18th if we needed it. I just didn't want anyone to be surprised if Ansible-3.0.0 shows up a few days late! Thanks, -Toshio On Tue, Feb 9, 2021 at 3:59 PM Toshio Kuratomi wrote: > >

[ansible-devel] Ansible-3.0.0 release candidate 1

ocs/docsite/rst/porting_guides/porting_guide_3.rst Thanks for testing! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansibl

[ansible-devel] Re: Ansible-2.10.7 released.

Small correction. The pip install instructions should read: $ pip uninstall ansible $ pip install ansible==2.10.7 --user Thanks! -Toshio On Tue, Feb 9, 2021 at 1:28 PM Toshio Kuratomi wrote: > > Hi all, > > We're happy to announce that the ansible-2.10.7 package is now

[ansible-devel] Ansible-2.10.7 released.

Hi all, We're happy to announce that the ansible-2.10.7 package is now available! This update contains bugfixes and new, backwards compatible features in the contained collections. Ansible-2.10.x is a big change in how the Ansible package is built so if you missed out on all the changes that have

[ansible-devel] Ansible-3.0.0 beta1 released

Hi all, We're happy to announce that the ansible-3.0.0 beta1 package is now available! This update is based on the ansible-base-2.10.x package just like ansible-2.10 was so the changes shouldn't be too major. However, it does contain new major versions of many collections which means that there wi

[ansible-devel] Ansible-2.10.6 has been released

Hi all, We're happy to announce that the ansible-2.10.6 package is now available! This update contains bugfixes and new, backwards compatible features in the contained collections. Ansible-2.10.x is a big change in how the Ansible package is built so if you missed out on all the changes that have

[ansible-devel] Ansible-2.10.3 released: quick fix for installation issue

ible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email

[ansible-devel] Re: Ansible-2.10.2 has been released

at 4:42 PM Toshio Kuratomi wrote: > > Hi all- > > We're happy to announce that the ansible-2.10.2 package is now > available! This update contains bugfixes and new, backwards > compatible features in the contained collections as well as bringing > in ansible-base-2.10.3 as

[ansible-devel] Ansible-2.10.2 has been released

ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to a

[ansible-devel] Ansible-2.10.1 has been released

#x27;re in the early stages of discussion. Porting Help - There's a unified porting guide for collections which have opted-in. You can find that at: https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi --

[ansible-devel] Ansible-2.10.0 has been released!

om/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, se

[ansible-devel] Ansible-2.10.0 release candidate 1

ou aren't sure where your bug falls, pick which you feel is closest and the Community Team will always move it if needed. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this g

[ansible-devel] Re: Nominating blockers to 2.10.0 [Was Re: Ansible 2.10.0 beta 1]

ode.net/kb/answer/registration I highly recommend registering and testing that you are able to participate in #ansible-community discussions before the meeting on the 17th! -Toshio On Thu, Sep 10, 2020 at 8:29 AM Toshio Kuratomi wrote: > > Howdy folks! > > We're entering the final

[ansible-devel] Re: Ansible 2.10.0 beta 1

t 11:21 PM Toshio Kuratomi wrote: > > Hi all- > > For all those wanting to test the next version of Ansible, we're happy > to announce that Ansible 2.10.0 beta1 is now available on PyPI! > > Ansible 2.10.0b1 pulls in the ansible-base-2.10.1 (presently rc2) > package v

[ansible-devel] Nominating blockers to 2.10.0 [Was Re: Ansible 2.10.0 beta 1]

n towards fixing anything that wasn't noticed previously in the Ansible-2.10.1 release. So please test out the beta and release candidate now and report candidate blockers before the meeting. Thank you, Toshio Kuratomi On Tue, Sep 1, 2020 at 11:21 PM Toshio Kuratomi wrote: > > Hi all- &

[ansible-devel] Ansible-2.10.0 beta2

ser-testing-of-ansible-2.10-pre-releases If you aren't sure where your bug falls, pick which you feel is closest and the Community Team will always move it if needed Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Devel

[ansible-devel] Changes to the ansible-2.10.0 pre-release schedule

://raw.githubusercontent.com/ansible/community/master/meetings/ical/community.ics * 22-Sep-2020: If no blockers are found, ansible-2.10.0 final will release as previously scheduled. Thanks for understanding! -Toshio Kuratomi -- You received this message because you are subscribed to the Google

[ansible-devel] Ansible 2.10.0 beta 1

k which you feel is closest and the Community Team will always move it if needed Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send a

[ansible-devel] Ansible-2.10.0: Unfrozen until beta1

Greetings collection maintainers! I have an important update to the Ansible-2.10.0 release schedule that affects you. == Summary: The important bits == I announced feature freeze for Ansible 2.10.0 last week. However, after a group of collections told me that they have a coordinated new feature

[ansible-devel] Ansible 2.10.0 collection versions now feature frozen

Greetings all, in preparation for the beta1 release on the first of September, the ansible package is now feature frozen. What does that mean exactly? The main goal of the 2.10.x package is to give end users a smooth transition from the monolitihic approach to content in ansible-2.9 to the ecosys

[ansible-devel] Ansible 2.10.0 alpha 9

draft document which includes where to report bugs on various parts of the ansible package: https://github.com/ansible/community/wiki/User-testing-of-ansible-2.10-pre-releases If you aren't sure where your bug falls, pick which you feel is closest and the Community Team will always move it if

[ansible-devel] Ansible 2.10.0 alpha 8

nity/antsibull If you aren't sure where to file the bug, pick which you feel is closest and the Community Team will always move it if needed Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscr

Re: [ansible-devel] revisiting empty option for file module

I don't have answers to your question but I wonder about your use case. Directories are seldom left empty so it seems like this is more about taking action to empty a directory than it does to assert that the state of the system includes the emptied directory. That can be an important distinction

[ansible-devel] Ansible 2.10.0 alpha 7

he way the new ansible is packaged: https://github.com/ansible-community/antsibull If you aren't sure where to file the bug, pick which you feel is closest and the Community Team will always move it if needed Thanks! -Toshio Kuratomi -- You received this message because you are subscr

[ansible-devel] Schedule for the ansible (as opposed to ansible-base) 2.10 release

Hi all, Ansible-2.10 has been a big change in how we develop Ansible with development split between the ansible-base and ansible packages. Although the development schedule has been known for a long time, we're only finalizing the release schedule for Ansible-2.10.0 now. Here is the release schedu

[ansible-devel] Ansible 2.10.0 alpha 6

ere: https://github.com/ansible-collections/ * Bugs in the way the new ansible is packaged: https://github.com/ansible-community/antsibull If you aren't sure where to file the bug, pick which you feel is closest and the Community Team will always move it if needed Thanks! -Toshio Kuratomi --

[ansible-devel] Ansible 2.10.0 alpha 4

elevant collection repo, normally one of the repos here: https://github.com/ansible-collections/ * Bugs in the way the new ansible is packaged: https://github.com/ansible-community/antsibull If you aren't sure where to file the bug, pick which you feel is closest and the Community Team wil

[ansible-devel] Ansible-2.10.0 alpha3

m/ansible-community/antsibull If you aren't sure where to file the bug, pick which you feel is closest and the Community Team will always move it if needed Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development&

[ansible-devel] New release: Ansible 2.10.0a1

e: https://github.com/ansible-collections/ * Bugs in the way the new ansible is packaged: https://github.com/ansible-community/antsibull If you aren't sure where to file the bug, pick which you feel is closest and the Community Team will always move it if needed Thanks! -Toshio Kuratomi -- You re

Re: [ansible-devel] New Ansible package name dual install hazard?

l behaves, as opposed > to "pip install ansible", after the release happens. > > Alan > github: AlanCoding > > > On Fri, May 1, 2020 at 1:01 PM Toshio Kuratomi > wrote: > >> Where are you getting ansible-base from? The best solution might be to >> put

Re: [ansible-devel] ansible task to cat a file with sql commands and pipe the commands into database using psql with synchronise module (remotely)

What happens if you use shell instead of command? I'm not 100% certain but I think what's happening is that since you're using the ansible command module instead of the shell module, it is running the equivalent of: cat '/var/lib/pgsql/temp/truncate_sql' '/var/lib/pgsql/temp/postcodesio-*' '|' '

[ansible-devel] Minor change to the license listed in the project's README to GPLv3+

Greetings all, I'm just letting you all know that I'm merging this PR today: https://github.com/ansible/ansible/pull/65124 It changes the license listed in the README from "GNU General Public License v3.0" to "GNU General Public License v3.0 or later". We consider this a clarification rather tha

[ansible-devel] New Ansible release 2.9.0

you upgrade to 2.9.0, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are

[ansible-devel] New Ansible releases 2.8.6, 2.7.14, 2.6.20, and 2.9.0rc4

discover any errors or if any of your working playbooks break when you upgrade to 2.8.6, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Than

[ansible-devel] New Ansible release 2.9.0rc3

aybooks break when you upgrade to 2.9.0rc3, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You re

[ansible-devel] New Ansible release 2.9.0rc2

ose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving em

[ansible-devel] New Ansible pre-release 2.9.0rc1

upgrade to 2.9.0rc1, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because

[ansible-devel] New Ansible release 2.8.5

com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this

[ansible-devel] Ansible release 2.9.0b1, feature freeze, and stable-2.9 branching

new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop rec

[ansible-devel] New Ansible releases 2.8.4, 2.7.13, and 2.6.19

e/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this grou

[ansible-devel] New Ansible release 2.8.3

le/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and sto

[ansible-devel] Re: New Ansible releases 2.8.2, 2.7.12, and 2.6.18

One additional note: The Deb builds for the Ansible PPA failed. We're working on getting those built and uploaded but no ETA yet. (Tomorrow is a US holiday so it cuts into the time available to diagnose, fix, and then release those). -Toshoi On Wed, Jul 3, 2019 at 1:56 PM Toshio Kuratomi

[ansible-devel] New Ansible releases 2.8.2, 2.7.12, and 2.6.18

e version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubsc

[ansible-devel] New Ansible releases 2.8.1

le/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and

[ansible-devel] New Ansible releases 2.7.11 and 2.6.17

ou upgrade to 2.7.11, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because

[ansible-devel] New Ansible release 2.8.0

eport the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Deve

[ansible-devel] Upstream Ansible 2.8.0rc2 released

0rc2, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to th

[ansible-devel] New Ansible release, 2.8.0rc1

https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group.

[ansible-devel] Ansible-2.8.0b1 available for testing

e to 2.8.0b1, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. Thanks! -Toshio Kuratomi -- You received this message because you are subscr

[ansible-devel] beta1 delayed until Monday

We've spent all day working on timeouts and failures in web services that we're testing against so we're not going to have time to get beta1 out the door before people have to leave work today. New estimate for beta1 is Monday of next week. If we get it out the door then, we should be able to avo

[ansible-devel] Ansible-2.8.0beta1 delayed one day

he release date of 2.8.0 final. Thanks -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.c

Re: [ansible-devel] Ansible-2.8.0 delay

> modules/plugins) to any code > 2019-04-25 Release Candidate 1 > 2019-05-02 Release Candidate 2 (if needed) > 2019-05-09 Release Candidate 3 (if needed) > 2019-05-16 Release > > So are above dates confirmed? > > Thanks > Martin > > On Fri, Mar 22, 201

[ansible-devel] New Ansible release 2.7.10 and 2.6.16

. If you discover any errors or if any of your working playbooks break when you upgrade to 2.7.10, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn

[ansible-devel] Re: Ansible-2.8.0 delay

On Thu, Mar 21, 2019 at 5:07 PM Toshio Kuratomi wrote: > > Hello all, > > As some of you may have noticed, Ansible-2.8.0-alpha1 has been delayed. It > was scheduled for last week but we have one important feature that we're > still working on. To give it a chance t

[ansible-devel] Ansible-2.8.0 delay

Hello all, As some of you may have noticed, Ansible-2.8.0-alpha1 has been delayed. It was scheduled for last week but we have one important feature that we're still working on. To give it a chance to be finished up, we've slipped Alpha by two weeks (now due out on Thursday, next week) and slippe

[ansible-devel] Ansible 2.7.9 and 2.6.15

s, or if you see any regressions from playbooks which work on 2.7.8 and prior, please open a GitHub issue, and be sure to mention you're using 2.7.9. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group.

[ansible-devel] Ansible 2.7.8, 2.6.14, and 2.5.15

on you're using 2.7.8. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@go

[ansible-devel] Should we drop Fedora rpms from https://releases.ansible.com/ ?

Hey all, I just sent an email to ansible-project, requesting feedback on the idea of dropping Fedora builds from https://releases.ansible.com/ (The Fedora Project itself would still provide rpms in their repositories). If you are interested in that, please reply to the relevant post on the ansibl

[ansible-devel]

s://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html to help migrate your content to 2.7. If you discover any errors, or if you see any regressions from playbooks which work on 2.7.6 and prior, please open a GitHub issue, and be sure to mention you're using 2.7.7. Thanks!

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

On Mon, Jan 21, 2019 at 9:41 AM Vitezslav Vit Vlcek wrote: > > I can summarize outcome of my research. Could you point me to right direction? > > I found faq for windows > https://github.com/ansible/ansible/blob/d1c0b7a597944baed20af28c8833d51451791f69/docs/docsite/rst/user_guide/windows_faq.rst

Re: [ansible-devel] Support for IBM z/OS on ansible nodes

On Mon, Jan 21, 2019 at 9:05 AM Aaron Surty wrote: > > It seems like Vitek's issue of executing untagged ASCII python modules on > z/OS is not unique. I'm going to try and investigate why that works for me > and not others, but in the meantime perhaps there should be a blurb in the > FAQ that

[ansible-devel] Ansible 2.7.6 and 2.6.12

s, or if you see any regressions from playbooks which work on early releases, please open a Github issue, and be sure to mention which Ansible release you're using. Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Deve

[ansible-devel] Ansible 2.5.14, 2.6.11, and 2.7.5 are available

Changelog: https://github.com/ansible/ansible/blob/v2.5.14/changelogs/CHANGELOG-v2.5.rst SHA256: 695ac8ebce0be57062924ff90f4b98cd61caa99cd21cdb10a964e3320524a069 ansible-2.5.14.tar.gz -Toshio Kuratomi (@abadger1999) -- You received this message because you are subscribed to the Google Groups

Re: [ansible-devel] Question on Ansible *NIX packages with Python3 dependencies

Red hat Enterprise Linux 7 ships with python 2.7 so we won't be able to switch to python 3 there. You could take a look at the Fedora packages of ansible, though, i believe that they've switched over to building against python3 in the current releases and you can probably adapt the spec file to yo

[ansible-devel] Ansible-2.7.2

rting_guides/porting_guide_2.7.html to help migrate your content to 2.7. If you discover any errors, or if you see any regressions from playbooks which work on 2.6.x and prior, please open a Github issue, and be sure to mention you're using 2.7.2. Thanks! -Toshio Kuratomi -- You re

[ansible-devel] Ansible-2.7.1 is released

d be sure to mention you're using 2.7.1. Thanks! -Toshio Kuratomi (abadger1999) -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-deve

[ansible-devel] Ansible-2.7.0rc4 released

mention you're using 2.7.0rc4 Thanks! Toshio Kuratomi (abadger1999) Ansible 2.7 release manager -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send

[ansible-devel] Ansible-2.7.0rc3

Hi all- we're happy to announce that the general release of Ansible 2.7.0rc3 is now available! How do you get it? -- $ pip install ansible==2.7.0rc3 --user The tar.gz of the release can be found here: https://releases.ans

[ansible-devel] Ansible 2.7.0rc2

Hi all- we're happy to announce that the general release of Ansible 2.7.0rc2 is now available! How do you get it? -- $ pip install ansible==2.7.0rc2 --user The tar.gz of the release can be found here: https://releases.ans

Re: [ansible-devel] When can we remove the prohibition on requests?

On Thu, Sep 13, 2018 at 11:52 AM, Matt Martz wrote: >> For your point, though, the API is both well known to developers and >> much better designed than open_url/fetch_url > > > I'm not necessarily disagreeing here, but do you have something specific you > are referring to? What about requests is

Re: [ansible-devel] When can we remove the prohibition on requests?

On Thu, Sep 13, 2018 at 11:30 AM, Brian Coca wrote: > It is not a question about pet peeves, its a question about the installed > base. > Just because you say this doesn't make it so. I brought information to the table. You need to do the same. -Toshio -- You received this message because yo

Re: [ansible-devel] When can we remove the prohibition on requests?

ver about the > requests version for me. It was about yet another unnecessary dependency. > > What is the driving factor behind wanting to allow it? > > On Thu, Sep 13, 2018 at 11:10 AM Toshio Kuratomi > wrote: >> >> When RHEL5 went EOL we talked about dropping

[ansible-devel] When can we remove the prohibition on requests?

When RHEL5 went EOL we talked about dropping the prohibition on modules using the requests library (directly many modules use requests indirectly through their dependencies) but someone said "there's other distros than RHEL5 using 1.x versions of requests." (and according to that person, the 1.

[ansible-devel] Ansible 2.7.0rc1

. The full changelog is at: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst If you discover any errors, or if you see any regressions from playbooks which work on 2.6.x and prior, please open a Github issue, and be sure to mention you're using 2.7.0rc1 T

[ansible-devel] Ansible-2.7.0 beta 1 is now available

ing_guides/porting_guide_2.7.html to help migrate your content to 2.7. If you discover any errors, or if you see any regressions from playbooks which work on 2.6.x and prior, please open a GitHub issue, and be sure to mention you're testing against 2.7.0b1. Thanks! Toshio Kuratomi (abadger199

[ansible-devel] Ansible 2.4.4 RC2 is ready for testing

4.x if critical bugs are discovered. Non-critical bugfixes will be released in the 2.5.x or newer release serieses.) Thanks for testing! Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this

Re: [ansible-devel] [Urgent] Python 2.7 or python 3.x for fresh project

Ansible will work with both. You are starting your project at a time when most other projects support both but the weight of past work has been with python 2 and the focus of future work by most projects is on python3. -Toshio On Sun, Mar 25, 2018, 11:13 PM Akash Agarwal wrote: > Hi All, > > W

[ansible-devel] Ansible 2.4.4 RC1 is ready for testing

candidate. -- I'm aiming to have 2.4.4 final come out the week after 2.5.0 final is out. So do test this out if you're intending to stay on 2.4.x a while longer but note that the final of 2.4.4 won't be released until after 2.5.0. Thanks!

[ansible-devel] Re: ANSIBALLZ_WRAPPER is not recognized as the name \r\nof a cmdlet

On Tuesday, February 27, 2018 at 11:16:28 PM UTC-8, Guillem Sola wrote: > > Hi, > > I'm trying to run some integration tests from ubuntu against a windows10 > host with > > ./ansible-test windows-integration -v win_xml --allow-destructive > > Test tasks starts but it complains > > fatal: [window

  1   2   >