David Flanagan 544d37bbc4 fix: "Injecting..." status stirng can be omitted by log levels ...

When using `infisical run`, I am often running another command
that needs to be processed or consumed by another; such as:

infisical run -- supabase status -o env

The Injecting string was being printed directly to stdout and
stopping such scripting from being successful, without further
adding tail -n+2.

This change defaults the output to the INFO logging level, which
means the behaviour is the exact same for everything; however
those who wish can omit this output with -l error|fatal

2023-12-10 16:13:38 +00:00

..

pre-commit-script

Add auto install pre commit

2023-05-23 00:09:00 -04:00

agent.go

add docs for folder cli command

2023-11-29 09:57:45 -05:00

cmd_test.go

nit: method name change

2023-02-24 22:21:20 -05:00

export.go

Revert "keyring swap, better error messages/warnings, delay upgrade notif"

2023-08-01 22:55:19 -04:00

folder.go

remove init from folders cmd

2023-11-28 19:30:08 -05:00

init.go

swap out keyring package

2023-08-02 10:11:23 -04:00

login.go

change broswer based login from localhost to 127.0.0.1

2023-10-05 11:19:29 -04:00

man.go

fix copyright label in go source

2023-02-02 19:45:24 +05:30

reset.go

link to forked keyring and bring back vault command

2023-08-17 15:07:12 -04:00

root.go

add telemetry to cli

2023-05-19 00:16:26 -04:00

run.go

fix: "Injecting..." status stirng can be omitted by log levels

2023-12-10 16:13:38 +00:00

scan.go

catch case when hook path is default

2023-05-23 19:34:31 -04:00

secrets.go

add docs for folder cli command

2023-11-29 09:57:45 -05:00

tokens.go

patch crypto in create service token in cli

2023-09-28 19:27:38 -07:00

user.go

add create service token to cli + docs for it

2023-09-27 21:07:54 -07:00

vault.go

link to forked keyring and bring back vault command

2023-08-17 15:07:12 -04:00