[ansible-devel] module_set_locale default changed for 2.2 -- module authors need to set environment variables when screenscraping output

Greetings all, For 2.2 we're making a change to when Ansible sets the LC_ALL and LANG environment variablesfor running modules. Here's what that means for you: Executive summary for users: If you notice Ansible modules in devel throwing errors because the module is not finding a string it

Re: [ansible-devel] Re: Ansible 2.1.0 RC4 is ready for testing

Just an update for the mailing list -- we finished reviewing and merging this too late for 2.1.0 but it is now merged into the stable-2.1 branch for inclusion into 2.1.1. -Toshio On Mon, May 23, 2016 at 7:23 AM, Bernhard L. wrote: > Hi, >> >> > It would be nice if this issue

[ansible-devel] Time frame for end of support for Python-2.4 and Python-2.5 on managed machines

/distribution or on how they can install and support a newer version of Python on their older machines. 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 fro

[ansible-devel] Python3 -- where are we now?

Hey everyone, just dropping a short status update on the progress on getting Ansible running on python3. Bad news first: I don't think that Ansible-2.2 on python3 will be production ready. There are large pieces of the controller side code that I haven't yet looked at or tested heavily and the

Re: [ansible-devel] PR to update kinesis_stream module has been opened for 3 months but no one looked at it

An Ansible AWS SIG was recently formed. If you are on IRC, they have a channel on irc.freenode.net: #ansible-aws. I've mentioned the PR there as well but it's always better if the PR submitter shows up to ask for review and respond to any requests for changes. -Toshio On Thu, Aug 3, 2017 at

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

testing against this release candidate. 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...@google

[ansible-devel] Ansible 2.4.0 RC4 is ready for testing

see any regressions from playbooks which work on 2.3.x and prior, please open a Github issue and be sure to mention you're testing against this release candidate. Thanks! Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development&q

[ansible-devel] Re: Ansible 2.4.0 RC3 is ready for testing

On Wed, Sep 13, 2017 at 3:50 PM, Toshio Kuratomi <tkura...@redhat.com> wrote: > Note that we're still on track for final release on the 19th. Towards > that end we're planning on having one more rc with code changes on > Saturday, the 16th. Unless blocker regressions are

[ansible-devel] Ansible 2.4.0 RC3 is ready for testing

with the updated documentation rather than to get additional testing as rc4 should be equivalent to rc5 in terms of code. I'll send out an update in the rc4 or rc5 release announcement if any of these plans change. Thanks! Toshio Kuratomi -- You received this message because you are subscribed

Re: [ansible-devel] Solaris 10 - '~' directory created in home directory - unarchive fails

ursday, October 12, 2017 at 10:03:10 AM UTC-5, Toshio Kuratomi wrote: >> >> I believe there is a bug for this open[1]_. If you change remote_tmp >> to use $HOME instead of ~ I believe that workaround will fix your >> issue on Solaris (but may introduce a problem on platforms w

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

your own .tar.gz (output will be dist/ansible-2.4.0.0.tar.gz): $ make sdist If you discover any errors, or if you see any regressions from playbooks which work on 2.3.x and prior, please open a Github issue and be sure to mention you're testing against this release candidate. Thanks! Toshio

Re: [ansible-devel] Is there a process for expediting reviews of bug fixes and changes?

Joining us on irc is the best way. #ansible-devel on irc.freenode.net We get so many issues and PRs that we have a very large backlog. Showing up and being interested in the process of review and fix is the best way to get something merged quicker. Depending on what it is, having other people

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

are discovered in this release candidate, 2.4.1 final will be out next week. 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, sen

[ansible-devel] Re: [ansible-project] Ansible *2.4.1* RC1 is ready for testing

of these changes only affect running our test infrastructure, not the code used at runtime by end users, I'm not anticipating pushing an rc2 for these changes. I'l update the list if any blocking bugs are found which will require an rc2. -Toshio On Wed, Oct 11, 2017 at 10:45 PM, Toshio Kuratomi <tk

Re: [ansible-devel] Solaris 10 - '~' directory created in home directory - unarchive fails

I believe there is a bug for this open[1]_. If you change remote_tmp to use $HOME instead of ~ I believe that workaround will fix your issue on Solaris (but may introduce a problem on platforms where the HOME environment variable is not set). The problem ultimately comes down to Solaris 10 not

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

. So we've merged a fix for that and released 2.4.1.0-rc2 today. If no further blockers are discovered, we'll release 2.4.1 final next week. .. _[1]: https://github.com/ansible/ansible/issues/31857 Thanks! Toshio Kuratomi -- You received this message because you are subscribed to the Google

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

your own .tar.gz (output will be dist/ansible-2.3.3.0.tar.gz): $ make sdist If you discover any errors, or if you see any regressions from playbooks which work on 2.3.2 and prior, please open a Github issue and be sure to mention you're testing against this release candidate. Thanks! Toshio

Re: [ansible-devel] Re: Where is the webdocs file?

It should be run from a checkout of the source repository. The dev_guide documentation anticipate that you are developing ansible and working from a checkout. -Toshio On Nov 26, 2017 11:20 PM, "Jae Kim" wrote: Some replied "There isn't a file named webdocs, it's just a

Re: [ansible-devel] Re: Where is the webdocs file?

This doesn't seem like it is frozen. How long did you wait for it to finish? Did your CPU continue to be working hard during this time? There was a Sphinx version that did get stuck when building docs but in general, the docs build does take quite a while. It takes over an hour for me on

[ansible-devel] Ansible 2.4.2 Beta4 ready for testing

Hi all, we're happy to announce that beta4 for 2.4.2 is now available for testing. How do you get it? -- The tar.gz of the release can be found here: https://releases.ansible.com/ansible/ansible-2.4.2.0-0.4.beta4.tar.gz SHA256:

[ansible-devel] Ansible 2.4.2 beta2 is ready for testing

: Beta4 * November 22nd: Rc1 * November 29th: 2.4.2 final These dates could still be adjusted to try to work around Thanksgiving better and of course, if blockers are found in RC1 we'll have to slip into December for the final release. Thanks! Toshio Kuratomi -- You received this message because

[ansible-devel] Ansible 2.4.2 beta3 is ready for testing

November - 2.4.2-beta4 22nd November - 2.4.2-rc1 29th November - 2.4.2 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, sen

[ansible-devel] Ansible 2.4.3 Beta1 is ready for testing

Hi all, we're happy to announce that Beta1 for 2.4.3 is now available for testing. How do you get it? -- The tar.gz of the release can be found here: https://releases.ansible.com/ansible/ansible-2.4.3.0-0.1.beta1.tar.gz SHA256:

[ansible-devel] Re: Ansible 2.4.3 Beta1 is ready for testing

Minor correction: If we hit the Final/RC3 date that would be 24th of January, 2018; not 24th of December. -Toshio On Wednesday, December 6, 2017 at 7:54:17 PM UTC-8, Toshio Kuratomi wrote: > > > Tentative release schedule for 2.4.3 > > Beta1 6 Dec > Beta2 20 Dec

Re: [ansible-devel] Module design questions: digital_ocean_domain

ryansb and sivel commented on your question onIRC but it sounds like you'd already left for the day. Here's what they said: Good afternoon! I was wondering if someone could provide guidance on a design decision within the digital_ocean_domain module. I'm currently working with Akasurde to

[ansible-devel] Ansible 2.4.2 beta1 is ready for testing

merging the fixes that accumulated over the past few weeks of waiting for the release candidate to turn into final and put them into a beta tarball for everyone to start testing and finding the blocker bugs early so that we can have a solid 2.4.2 release. Thanks for testing! Toshio Kuratomi

[ansible-devel] Ansible-2.4.3-rc3

hoping that this will be the last release candidate before 2.4.3.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

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

ebruary 21, 2018 at 10:55:24 PM UTC-8, Toshio Kuratomi wrote: > > Hi all, we're happy to announce that Beta1 for 2.4.4 is now available > for testing. > > How do you get it? > -- > > The tar.gz of the rel

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

-dancing-days---tbd 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.com. For mo

[ansible-devel] Re: Ansible 2.4.4 Beta1 is ready for testing

y 21, 2018 at 10:55:24 PM UTC-8, Toshio Kuratomi wrote: > > Hi all, we're happy to announce that Beta1 for 2.4.4 is now available > for testing. > > How do you get it? > -- > > The tar.gz of the rel

Re: [ansible-devel] Ansible startup performance & time spent loading in ConfigManager

This is a good idea. For parsing playbooks we made this change a long time ago. Could you open a bug report on GitHub for this? With the holiday vacation coming up, I don't want this to be forgotten. Thanks, -Toshio On Dec 20, 2017 9:08 PM, wrote: > Hi all, > > I'm

[ansible-devel] Ansible-2.4.3 Beta3 is ready for testing

will probably switch over to accumulating minor bugfixs in the stable-2.4 tree and only making a release with them included if a large enough bug is discovered that warrants a 2.4.5. Thanks! Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "An

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

/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 (abadger1999) Ansible Core

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

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

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 group and stop

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

. -- 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! Toshio Kuratomi -- You

[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:

[ansible-devel] Ansible-2.7.0rc4 released

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 an email to ansible-deve

[ansible-devel] Ansible-2.7.1 is released

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-devel+unsubscr...@google

[ansible-devel] Ansible-2.7.2

.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 received this message because you

[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:

[ansible-devel] Ansible 2.7.6 and 2.6.12

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 Development" group. To u

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

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

[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

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

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

[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:

[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

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

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 the prohibition on >> modules using th

[ansible-devel] New Ansible release 2.7.10 and 2.6.16

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't. Thanks! -Toshio Kuratomi

Re: [ansible-devel] Ansible-2.8.0 delay

) 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, 2019 at 1:08 AM Toshio

[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

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

! -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.com. For more options, v

[ansible-devel] Ansible 2.7.9 and 2.6.15

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. To unsubscribe from

[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 to be

[ansible-devel]

/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! -Toshio Kuratomi -- You

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

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 the Google Groups

[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

[ansible-devel] New Ansible release 2.8.0

: 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. To u

[ansible-devel] New Ansible releases 2.8.1

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 emails fro

[ansible-devel] New Ansible releases 2.7.11 and 2.6.17

, 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

[ansible-devel] Upstream Ansible 2.8.0rc2 released

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 the Google Groups "An

[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 wrote

[ansible-devel] New Ansible release, 2.8.0rc1

/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

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

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.com. For mo

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

/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 receiving e

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

, 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 emails from it, sen

[ansible-devel] New Ansible release 2.8.5

/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 receiving emails fro

[ansible-devel] New Ansible release 2.8.3

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 emails fro

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

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 the Google Groups

[ansible-devel] New Ansible release 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 subscribed to the Google

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

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. Thanks! -Toshio Kuratomi -- You

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] New Ansible release 2.9.0rc3

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 received this message because you

[ansible-devel] New Ansible release 2.9.0rc2

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 emails from it, send an email to ans

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

; 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 a Dev version of ansi

[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

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 an email to ansible-devel+unsubscr...@googlegroups

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

/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 weeks of the An

[ansible-devel] Re: Ansible 2.10.0 beta 1

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 via a depende

[ansible-devel] Ansible-2.10.0 release candidate 1

l 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 an email to an

[ansible-devel] Ansible-2.10.0 beta2

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 Development" group. To unsubscribe from this group

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

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- > > For all those wanting to t

[ansible-devel] Ansible-2.10.1 has been released

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 -- You received this message because

[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

[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

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

ting_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 ansible-devel+unsubscr...@g

[ansible-devel] Ansible 2.10.0 alpha 8

e 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 unsubscribe from this group and stop receiving emails from it,

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

[ansible-devel] New release: Ansible 2.10.0a1

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 subscribed to the Google Group

[ansible-devel] Ansible 2.10.0 alpha 4

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 rec

[ansible-devel] Ansible-2.10.0 alpha3

e 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 unsubscribe from this group and stop receiving emails

[ansible-devel] Ansible 2.10.0 alpha 6

ay 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 subscribed to the Googl

[ansible-devel] Ansible 2.10.0 alpha 7

le-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" group.

[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

[ansible-devel] Ansible 2.10.0 alpha 9

o 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 needed Thanks! -Toshio Kuratomi -- You rec

[ansible-devel] Ansible-2.10.2 has been released

/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 ansible-devel+unsubscr...@google

[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 a de

  1   2   >