fix(main): unmark endpoint as sensitive

[wyardley]

It doesn't appear there's any clear reason that the endpoint output needs to be sensitive.
Fixes #2248

[apeabody]

/gcbrun

[wyardley]

@apeabody may have missed some, but took a first pass at updating tests.

Do you have any more context on why it may have been set this way originally?

[apeabody]

@apeabody may have missed some, but took a first pass at updating tests.

Do you have any more context on why it may have been set this way originally?

Hi @wyardley - I do no know, but it appears it has been this way since at least early 2019. I'm checking with the broader team if there is a reason not to change. Cheers!

[apeabody]

/gcbrun

[apeabody]

Thanks for the contribution @wyardley!

Agreed - sensitive is primarily needed for passwords, tokens, and private certs.

[apeabody]

/gcbrun

[wyardley]

Agreed - sensitive is primarily needed for passwords, tokens, and private certs.

I thought maybe at some point, some variant of the endpoint had contained a secret maybe, but that doesn't seem super likely? I found the same thing that you did -- even digging through changes of filenames etc, it was hard to figure out in the git history why it was set this way. Thanks for quick review 🙏

[apeabody]

/gcbrun