What i do is assign the token to a variable. I typically copy the secret to my c...

Izkata · 2025-10-21T22:52:55 1761087175

I don't know how consistent this is across shells, but at least in bash putting a space before the command keeps it out of the history:

  $ ONE=1
  $  TWO=2
  $ echo $ONE $TWO
  1 2
  $ history | tail -n 4
   2002  clear
   2003  ONE=1
   2004  echo $ONE $TWO
   2005  history | tail -n 4

johnisgood · 2025-10-23T21:07:13 1761253633

Yeah, I have been using this feature of bash ever since its existence and it is quite handy at times, especially when I do "printf "<sensitive data>" | qr".

miningape · 2025-10-21T14:20:26 1761056426

this.

A while ago I was working on a DSL to solve this exact issue (env switching, http requests + chained requests e.g. to an auth server to retrieve a token) - but I haven't had the time recently, and I moved jobs to a GraphQL shop, so it feels a bit more pointless now :D

KORraN · 2025-10-21T15:10:01 1761059401

I love the second part of your tip, thank you.