[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0

2020-05-05 Thread c35...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christophe Le Guern commented on  JENKINS-60091  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HashiCorp Vault plugin using approle is not working since v3.0.0   
 

  
 
 
 
 

 
 Joseph Petersen thanks for checking. I tried, without success, to disable ssl verification since this is the biggest breaking change. For the record, here is my pipeline script: 

 

pipeline {
agent {
docker {
image 'xxx'
}
}

environment {
VAULT_ENTRY = vault path: 'dd/try-me', key: 'ansible', engineVersion: "1"
}stages {
stage("Vault try me") {
steps {
ansiColor('xterm') {
sh '''
echo $VAULT_ENTRY
echo "test"
'''
}
}
}
}
post { 
failure {
rocketSend emoji: ':jenkins:', rawMessage: true, message: "> :fire: [$JOB_NAME]($RUN_DISPLAY_URL) job #$BUILD_NUMBER *"+currentBuild.currentResult+"* :fire:"
}
}
}

 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0

2020-05-04 Thread joseph...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Petersen commented on  JENKINS-60091  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HashiCorp Vault plugin using approle is not working since v3.0.0   
 

  
 
 
 
 

 
 Christophe Le Guern That does not seem like a bug with the vault plugin. That seems like a bug with your pipeline script. Did you read the release notes? https://github.com/jenkinsci/hashicorp-vault-plugin/releases  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202936.1573144964000.21324.1588618860223%40Atlassian.JIRA.


[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0

2020-05-04 Thread c35...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christophe Le Guern reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Hello, I tried both versions 3.4.1 and 3.1.1 without success. Actual Jenkins version: 2.222.3   Here is the logs for 3.1.1 version:   

 

java.lang.IllegalArgumentException: One or more variables have some issues with their values: VAULT_ENTRY
	at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:433)
	at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.callClosureForMapEntry(CpsDefaultGroovyMethods:5226)
	at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.collect(CpsDefaultGroovyMethods:3446)
	at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.collect(CpsDefaultGroovyMethods:3463)
	at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:429)
	at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:78)
	at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withCredentialsBlock(ModelInterpreter.groovy:481)
	at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withCredentialsBlock(ModelInterpreter.groovy:480)
	at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:77)
	at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.inDeclarativeAgent(ModelInterpreter.groovy:590)
	at org.jenkinsci.plugins.docker.workflow.declarative.DockerPipelineScript.runImage(DockerPipelineScript.groovy:58)
	at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(Docker.groovy:127)
	at ___cps.transform___(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235)
	at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.constructorCall(DefaultInvoker.java:25)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:97)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
	at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
	at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:89)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)
	at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
	at sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
	at com.cloudbees.groovy.cps.impl.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39)
	at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
	at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28)
	at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55)
	at 

[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0

2020-04-21 Thread joseph...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Petersen resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in v3.1.1  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-60091  
 
 
  HashiCorp Vault plugin using approle is not working since v3.0.0   
 

  
 
 
 
 

 
Change By: 
 Joseph Petersen  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 https://github.com/jenkinsci/hashicorp-vault-plugin/releases/tag/hashicorp-vault-plugin-3.1.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 


[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0

2020-04-21 Thread joseph...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Petersen assigned an issue to Joseph Petersen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60091  
 
 
  HashiCorp Vault plugin using approle is not working since v3.0.0   
 

  
 
 
 
 

 
Change By: 
 Joseph Petersen  
 
 
Assignee: 
 Peter Tierno Joseph Petersen  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202936.1573144964000.15458.1587528720478%40Atlassian.JIRA.


[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0

2019-11-07 Thread mbr...@tradewindenergy.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcus Brown commented on  JENKINS-60091  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HashiCorp Vault plugin using approle is not working since v3.0.0   
 

  
 
 
 
 

 
 I believe this is the same issue as JENKINS-59836  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202936.1573144964000.10969.1573178700260%40Atlassian.JIRA.


[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0

2019-11-07 Thread c35...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christophe Le Guern created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60091  
 
 
  HashiCorp Vault plugin using approle is not working since v3.0.0   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Peter Tierno  
 
 
Components: 
 hashicorp-vault-plugin  
 
 
Created: 
 2019-11-07 16:42  
 
 
Environment: 
 Jenkins ver. 2.190.2  Hashicorp Vault Plugin: 3.0.0  Hashicorp Vault Pipeline Plugin: 1.3  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Christophe Le Guern  
 

  
 
 
 
 

 
 The Hashicorp Vault plugin was upgraded from 2.5.0 to 3.0.0 and pipelines don't work anymore. We are using an approle to login to Vault. Note: we don't have namespaces in our environment.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment