The tag-based lock behavior uses in-blueprint tags, rather than global catalog tags.
Note that the documentation cites the Terraform behavior which has also been adopted by customer internal automation tooling.
The ansible collection using in-blueprint tags has a couple of important implications:
- It won't be conflict-free with systems which rely on the original approach
- Recognizing and clearing the source of the problem isn't obvious to users
The tag-based lock behavior uses in-blueprint tags, rather than global catalog tags.
Note that the documentation cites the Terraform behavior which has also been adopted by customer internal automation tooling.
The ansible collection using in-blueprint tags has a couple of important implications: