Tag-based deployments with missing tags
Deployit 3.6.0 introduced tag-based deployments. Using tags, it is possible to guide Deployit in which deployables should be targeted to which containers. When only the deployable or container has tags set, but the other one doesn't, Deployit 3.6 will ignore the tags and fall back to generating deployeds based on types only.
Several customers requested that the implementation be changed such that if only one of the two sides has tags, Deployit treats that as a type-based match where there are no tags in common, so doesn't generate a mapping.
From Deployit 3.7, this will be the default behavior. Should you require this behavior in Deployit 3.6, you can use the attached hotfix.
Please sign in to leave a comment.