Container Exporter: Stop allowing channel as a parameter in custom tags

[christophermaier]

Hypothesis: the fact that the channel a particular Habitat package is currently in is not an intrinsic part of that package, and thus should not be provided as a parameter for creating a custom tag at container export time.

Furthermore, tags in Docker and channels in Builder are different enough that we probably shouldn't be conflating them (the "latest" tag in Docker is the closest thing to a "channel" that I can see).

Until Builder gets the ability to map promotions to container repository retaggings (as alluded to in habitat-sh/builder#376), we probably should not muddy the waters. It seems like if users want to reflect their Builder channels in their container repository tags, that is something best left to external tooling at the current time.

I think having channel as an option in our custom tagging scheme is confusing and potentially harmful, and should be removed. If there are dissenting voices on this topic, however, I would love to hear 🙇 😄

Aha! Link: https://chef.aha.io/features/APPDL-114

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.