Feature Request: Generate random passwords with CLI via dedicated command (e.g. `op generate`)

@1P_Amanda , that's what we're doing above already in this thread, see the original post for context.

Oops, I feel dumb now - that'll teach me to reply before coffee on a Monday morning. I'll make a note, thank you!

Amanda

Totally fine, I do that all the time too! Coffee is essential ☕️! Doesn't change the outcome in my case ;)

I'm not confident it would have in mine either, shhhh.

Defiantly suggest this as a separate function so it can be used without being authenticated; which can't be done for `op item create --dry-run ...`.

Suggestion have an option to run a command using `op generate`  as a command wrapper with an environment variable generated.

Such that an environment variable is briefly created in a environment where a passed command is run, and then safely destroyed with 100% certainty (even on error/crash).

E.g. `op generate password <<options>> -c 'store-secret add "example" --secret $GENERATED_PASSWORD' --confirmation $GENERATED_PASSWORD`.
Where GENERATED_PASSWORD is the environment variable created and `-c` is the command to be run.

The implementation could be something like:

// Note: Pseudo bash code, I'm not a bash programmer

// Create temp local evn var
GENERATED_PASSWORD=`op generate password <<options>>`

// Run given command
...

// Cleanup 
unset GENERATED_PASSWORD

// Add signal handling to cleanup GENERATED_PASSWORD

// Optionally (on by default) hook in to SDOUT/SDERR to redact the secret in output

Value add the extra complexity over just allowing the `op password` to be used directly:
 * Reduce the likely hood of secrets to be exposed accidentally
 * Cleanup handling on error
 * Way to showcase best practice in secrets management
 * Increase the value of the ("op") 1Password CLI/improve DevX
 * There are a lot of edge cases that 1Password can handle that would likely be too much work/missed for manual scripts