The callback yaml is deprecated.

[vbotka]

The recommended replacement is ANSIBLE_CALLBACK_RESULT_FORMAT=yaml

[ansible-documentation-bot[bot]]

Thanks for your Ansible docs contribution! We talk about Ansible documentation on Matrix at #docs:ansible.im if you ever want to join us and chat about the docs! We meet on Matrix every Tuesday. See the Ansible calendar for meeting details. We welcome additions to our weekly agenda items too. You can add the dawgs-meeting tag to a forum topic to bring it up at the next meeting.

[samccann]

Hi @vbotka and thanks for the PR! Can you tell me where you found this was deprecated? The deprecation should be noted in https://docs.ansible.com/ansible/devel/reference_appendices/config.html#envvar-ANSIBLE_STDOUT_CALLBACK but isn't there.

[vbotka]

Sure. Quoting from community.general.yaml callback:

DEPRECATED Removed in: version 13.0.0 Why: Starting in ansible-core 2.13, the ansible.builtin.default callback has support for printing output in YAML format. Alternative: Use result_format=yaml.

For details, please look at forum.ansible.com community.general.yaml has been deprecated

The DEPRECATION WARNING comes from the callback community.general.yaml. ANSIBLE_STDOUT_CALLBACK is not to blame.

JFYI, the fix ANSIBLE_CALLBACK_RESULT_FORMAT is an option of ansible.builtin.default callback.

[vbotka]

For the record: I'm not a new contributor. I've already contributed:

commit 5448661aec83fea3f353685310fea57abf20e140
Author: Vladimir Botka <[email protected]>
Date:   Thu Feb 3 21:40:04 2022 +0100

    Update 'Ansible and BSD' section 'Setting the Python interpreter'. (#76825)

commit 9a9ef01997557556e9a940f1f3f36b3bb3655398
Author: Vladimir Botka <[email protected]>
Date:   Thu Feb 3 21:29:25 2022 +0100

    Update 'Installing Ansible on FreeBSD'. (#76849)


    Co-authored-by: Abhijeet Kasurde <[email protected]>
    Co-authored-by: Sandra McCann <[email protected]>

commit 8c3e576cd578410cfd1969d612a61933f4382ed4
Author: Vladimir Botka <[email protected]>
Date:   Thu Oct 7 21:35:43 2021 +0200

    Fix docs get_url dest comment. Checksum does not prevent download if dest is dir. (#73185)

[gotmax23]

For the record: I'm not a new contributor. I've already contributed:

Thank you for your contributions! For now, the bot currently only considers issues and PRs made in the ansible-documentation repository when applying the new_contributor label.

[vbotka]

@gotmax23, I see . Thank you!

[patchback[bot]]

Backport to stable-2.17: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 2b8c2a0acabd0fc07f51ee03e28f67df802cabf3 on top of patchback/backports/stable-2.17/2b8c2a0acabd0fc07f51ee03e28f67df802cabf3/pr-2573

Backporting merged PR #2573 into devel

1. Ensure you have a local repo clone of your fork. Unless you cloned it from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these instructions you'll refer to it by the name upstream. If you don't have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible/ansible-documentation.git
   

3. Ensure you have the latest copy of upstream and prepare a branch that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2.17/2b8c2a0acabd0fc07f51ee03e28f67df802cabf3/pr-2573 upstream/stable-2.17
   

4. Now, cherry-pick PR #2573 contents into that branch:

   $ git cherry-pick -x 2b8c2a0acabd0fc07f51ee03e28f67df802cabf3
   

   If it'll yell at you with something like fatal: Commit 2b8c2a0acabd0fc07f51ee03e28f67df802cabf3 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 2b8c2a0acabd0fc07f51ee03e28f67df802cabf3
   

5. At this point, you'll probably encounter some merge conflicts. You must resolve them in to preserve the patch from PR #2573 as close to the original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2.17/2b8c2a0acabd0fc07f51ee03e28f67df802cabf3/pr-2573
   

7. Create a PR, ensure that the CI is green. If it's not — update it so that the tests and any other checks pass. This is it! Now relax and wait for the maintainers to process your pull request when they have some cycles to do reviews. Don't worry — they'll tell you if any improvements are necessary when the time comes!

🤖 @patchback I'm built with octomachinery and my source is open — https://github.com/sanitizers/patchback-github-app.

[gotmax23]

Thanks!

[patchback[bot]]

Backport to stable-2.18: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.18/2b8c2a0acabd0fc07f51ee03e28f67df802cabf3/pr-2573

Backported as https://github.com/ansible/ansible-documentation/pull/2655

🤖 @patchback I'm built with octomachinery and my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback[bot]]

Backport to stable-2.19: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.19/2b8c2a0acabd0fc07f51ee03e28f67df802cabf3/pr-2573

Backported as https://github.com/ansible/ansible-documentation/pull/2656

🤖 @patchback I'm built with octomachinery and my source is open — https://github.com/sanitizers/patchback-github-app.