This PR hides the up space attach flag --robot-token from help output. Users shouldn't need to provide this flag since robot tokens should be generated for them. And familiarity with other up commands might mislead a user into thinking they need to provide a personal access token. This hides the potential stumbling block while keeping it around in case it's helpful for debugging or workarounds.
Description of your changes
This PR hides the
up space attach
flag--robot-token
from help output. Users shouldn't need to provide this flag since robot tokens should be generated for them. And familiarity with otherup
commands might mislead a user into thinking they need to provide a personal access token. This hides the potential stumbling block while keeping it around in case it's helpful for debugging or workarounds.I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR, as appropriate.How has this code been tested
I ran
go run ./cmd/up space attach -h
and verified--robot-token
wasn't in help output.