Comment 2 for bug 1257587

How can this bug be fix committed? We currently completely ignore the tag being passed in and just write out a warning.

Surely this bug isn't fixed until we reject access through environment tags that don't use a UUID?

I was about to make a branch that caused names.NewEnvironTag to panic if the uuid wasn't a valid environ tag (matching uuid regex), but since this looks like a 1.21 change, we should wait a release.