vdo: Use yaml.safe_load() instead of yaml.load()

[leegarrett]

yaml.load() without specifying a Loader= is deprecated and unsafe.

For details, see
https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation

SUMMARY

Fixes #5631

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

vdo

[felixfontein]

Thanks a lot for your contribution! Can you please add a changelog fragment? Thanks.

[ansibullbot]

cc @bgurney-rh @rhawalsh
click here for bot help

[leegarrett]

Done, and also committed your suggestion. Thanks for the quick response!

[patchback]

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

❌ Failed to cleanly apply 428e181 on top of patchback/backports/stable-4/428e181440dc92378c7326d9d2bfadda052ce372/pr-5632

Backporting merged PR #5632 into main

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-collections/community.general.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-4/428e181440dc92378c7326d9d2bfadda052ce372/pr-5632 upstream/stable-4

4. Now, cherry-pick PR vdo: Use yaml.safe_load() instead of yaml.load() #5632 contents into that branch:

   $ git cherry-pick -x 428e181440dc92378c7326d9d2bfadda052ce372

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

   $ git cherry-pick -m1 -x 428e181440dc92378c7326d9d2bfadda052ce372

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR vdo: Use yaml.safe_load() instead of yaml.load() #5632 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4/428e181440dc92378c7326d9d2bfadda052ce372/pr-5632

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.

[patchback]

Backport to stable-5: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-5/428e181440dc92378c7326d9d2bfadda052ce372/pr-5632

Backported as #5636

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

[patchback]

Backport to stable-6: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-6/428e181440dc92378c7326d9d2bfadda052ce372/pr-5632

Backported as #5637

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

[felixfontein]

@leegarrett thanks a lot again for reporting and fixing this! :)