Hashicorp vault auth allow tokens directly set in TriggerAuthentication

[JorTurFer]

Report

Currently, hashicorp vault auth supports 2 login methods, one based on service account and other based on tokens.
The problem is that the token isn't provided from a secret but from the TriggerAuthentication directly. This is a security risk as TriggerAuthentication isn't a sensitive API by design:

Expected Behavior

The token should be recovered from a secret

Actual Behavior

The token is read from the TriggerAuthentication manifest

[shardulsrivastava]

I would like to work on this issue, can you pls assign it to me @JorTurFer.

[JorTurFer]

Nice! Thanks for your help 😄
As this issues has been there for a long time, we should support both ways at the same time to follow the deprecation policy. Basically, you have to add support to read the value from a secret OR the current approach (and we can eventually remove the support to the current approach after some versions)

[dttung2905]

Hello @shardulsrivastava are you working on it? If not, I can give it a try too

[shardulsrivastava]

@dttung2905 I am working on this right now.