No way to disable interactive login prompts

[ixxie]

Describe the bug

We are using the infisical CLI within our internal CLI. infisical run works great, but we are constantly getting burnt by outdated sessions causing our commands to hang.

I'm okay with our command just exiting with an informative message if infisical is logged in: the problem is, it seems very hard or impossible to do. I've been trying to have our CLI call infisical user get token to check if there is a session. The problem is that if there is no session, it triggers an interactive login session which neither --silent nor --plain disable.

To Reproduce

Try to create a cross-platform script that can check if there is an active infisical session.

Expected behavior

A --non-interactive flag would be awesome.

[maidul98]

Hi @ixxie , let us dig into this for you and follow up

[SujithThirumalaisamy]

@maidul98 I have tried this. And whenever I revoke the token in the ui and try infisical user get token its directly calling the interactive logic. A flag here can be very useful. By @ixxie suggession if --non-interactive flag sounds promising to you. I can work on it

[ixxie]

If you implement this, it may be good to also support setting this via env var.

[SujithThirumalaisamy]

I have tried adding a flag it worked. I will add the env as well. I will do a draft PR. Once the variable names are approved we will be good to go

[SujithThirumalaisamy]

As the GetCurrentLoggedInUserDetails func along with the block

if loggedInUserDetails.LoginExpired {
	loggedInUserDetails = EstablishUserLoginSession()
}

Is used in wide range of places. Will this flag be ideal to be implement at GetCurrentLoggedInUserDetails func level? because the cmd/pam.go is dependent on isConnected to decide wheather to login or just proceed. But its just a Get call.

We can also implement this in the EstablishUserLoginSession func level. But I am not sure if this will be an Ideal choice.

[SujithThirumalaisamy]

I guess this have be implemented in this specific way as the --token flag makes the thing non-interactive by default. You can use service token to fix this untill this thread is getting resolved