Background

The kpack CLI currently supports additional tags. This field was included in response to feedback from users that allowing them to have some measure of control over the tagging strategy when managing image resources was needed compared to being locked in to kpack's default tagging strategy. The additional tag field is primarily used to communicate semantic information. The two most common use cases we've heard is to append a version or source revision. This information is used to better track the source used to build the image.

Problem

Currently, the additional tags field only appends them. This makes it difficult to accomplish the two common use cases stated above. Users can identify the tags they don't want and delete them, but a more desired behavior to communicate semantic meaning with the additional tags field would be to give users the option to overwrite previous tags with a new one.

Feature Acceptance Criteria

In addition to the existing additional tags functionality, users can optionally choose to remove all existing additional tags with a new specified string.