skip_tags foo::bar` is split on the namespace separator `::` and expanded to `['foo::bar', 'foo', 'bar']`. Because resources are tagged with all parent tags, this means that every resource in the `foo` namespace is skipped when `
skip_tags foo::bar` is used. The same expansion issue was addressed for the `
tags` flag in
PUP-4495
, but it appears that the expansion logic for `
tags` and `
-skip_tags` is separate.
`{{--skip_tags foo::bar`}} is split on the namespace separator ` {{::`}} and expanded to ` {{['foo::bar', 'foo', 'bar']`}}. Because resources are tagged with all parent tags, this means that every resource in the `foo` namespace is skipped when ` {{--skip_tags foo::bar`}} is used. The same expansion issue was addressed for the ` {{--tags`}} flag in PUP-4495, but it appears that the expansion logic for ` {{--tags`}} and ` {{--skip_tags`}} is separate.
{{\--skip_tags foo::bar}} is split splits the tag on the namespace separator {{::}} and expanded expands to skip the set {{['foo::bar', 'foo', 'bar']}}. Because resources are tagged with all parent tags, this means that every resource in the `foo` namespace is skipped when {{\--skip_tags foo::bar}} is used. The same expansion issue was addressed for the {{\--tags}} flag in PUP-4495, but it appears that the expansion logic for {{\--tags}} and {{\--skip_tags}} is separate.
Tags specified via --skip_tags are no longer expanded by splitting on "::". This brings the behavior in line with how tags specified via --tags are handled. The behavior of --tags was fixed in PUP-4495.