snap_alias: fix regex expression when listing aliases

[russoz]

SUMMARY

While testing integration tests for ubuntu bumped into an error because the regular expression expected snap names to match [\w-]+ but in Ubuntu there comes one named lxd.lxc. Replacing with \S+.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

snap_alias

[felixfontein]

This needs a changelog fragment.

[Andersson007]

bot_status

[ansibullbot]

Components

changelogs/fragments/6361-snap-alias-regex-bugfix.yml
support: community
maintainers:

plugins/modules/snap_alias.py
support: community
maintainers: russoz

tests/integration/targets/snap_alias/aliases
support: community
maintainers:

Metadata

waiting_on: maintainer
changes_requested_by: null
needs_info: False
needs_revision: False
needs_rebase: False
merge_commits: []
too many files or commits: False
mergeable_state: clean
ci_status: success
maintainer_shipits (module maintainers): 1
community_shipits (namespace maintainers): 0
ansible_shipits (core team members): 0
shipit_actors (maintainers or core team members): russoz
shipit_actors_other: []
automerge: automerge shipit test failed

click here for bot help

[patchback]

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

❌ Failed to cleanly apply 4171418 on top of patchback/backports/stable-5/4171418e37d9eeab4fa0005528f8ee12008949de/pr-6361

Backporting merged PR #6361 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-5/4171418e37d9eeab4fa0005528f8ee12008949de/pr-6361 upstream/stable-5

4. Now, cherry-pick PR snap_alias: fix regex expression when listing aliases #6361 contents into that branch:

   $ git cherry-pick -x 4171418e37d9eeab4fa0005528f8ee12008949de

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

   $ git cherry-pick -m1 -x 4171418e37d9eeab4fa0005528f8ee12008949de

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

   $ git push origin patchback/backports/stable-5/4171418e37d9eeab4fa0005528f8ee12008949de/pr-6361

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-6: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-6/4171418e37d9eeab4fa0005528f8ee12008949de/pr-6361

Backported as #6378

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

[felixfontein]

@russoz thanks for your contribution!