I'm using HashCorp Vault pluging in Jenkins multibranch pipeline with Vault Token Credential configuration. Everything was fine until the newest version 2.3.0. When I updated the version from 2.2.0 to 2.3.0 all of my pipelines using vault wrapper settings start showing me in the console output of every Jenkins job the message from the summary of the issue -> `Vault credentials not found secret/<secret-name> `. When I go back to 2.2.0 everything works fine again. Before revert back to 2.2.0 I have changed all the steps as it is described here -> https://wiki.jenkins.io/display/JENKINS/HashiCorp+Vault+Plugin for version 2.3.0 but nothing changed.. again the same message.
I'm using HashCorp Vault pluging in Jenkins multibranch pipeline with Vault Token Credential configuration. Everything was fine until the newest version 2.3.0. When I updated the version from 2.2.0 to 2.3.0 all of my pipelines using vault wrapper settings start showing me in the console output of every Jenkins job the message from the summary of the issue -> ` *Vault credentials not found secret/<secret-name> `*. When I go back to 2.2.0 everything works fine again. Before revert back to 2.2.0 I have changed all the steps as it is described here -> [https://wiki.jenkins.io/display/JENKINS/HashiCorp+Vault+Plugin] for version 2.3.0 but nothing changed.. again the same message.
Upgrading to v2.3.1 allows you to set your vault engine on the Vault Configuration. It will default to version 2 so if it still fails you will most likely have to set it to version 1.