@Tailscale is it possible that an api call to a webservice which in turn calls the ts api to remove a machine from a tailnet would cause a net::ERR_NETWORK_CHANGED error to occur on other machines on that tailnet, causing that original api call’s server response to be interrupted
Would be real nice if the @Tailscale API had an endpoint that would tell you when the API key you’re using is due to expire so clients could help drive necessary renewal processes
@maisem_ali@Tailscale Works! Sorry, RTFM error. Still might be nice to include expiry as a resp hdr so it can be managed w middleware. Is the :keyid always guaranteed to be split(‘-‘)[1] parseable from the key itself to match which key is used? Would have assumed keys should be treated as opaque.
@bradfitz Where “drive necessary renewal processes” is like hitting a Slack webhook to remind #tailscale-admins to get off their butt and renew the API key ahead of the expiry 😉