Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Done
-
Component/s: pipeline-model-definition-plugin
-
Labels:None
-
Environment:Pipeline Config 0.1
-
Similar Issues:
Description
What would be nice and idiomatic is to be able to something like:
environment { AWS_ACCESS_KEY_ID = credentials(id='amazonKeyId') AWS_ACESS_KEY_SECRET = credentials(id='passwordId') }
(or something more configgy looking). This can be limited to the single secret case if needed (ie not username/password).
Using various incarnations of the wrapper:
withCredentials([[$class: 'UsernamePasswordMultiBinding', credentialsId: '', passwordVariable: 'AWS_SECRET', usernameVariable: 'AWS_ID']]) { // some block }
You can, I think get credentials back out but it is seems less configgy for common scenarious.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Environment | Pipeline Config 0.1 |
Assignee | Andrew Bayer [ abayer ] | rsandell [ rsandell ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Resolution | Done [ 10000 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
So I'm wondering if it might actually make more sense to do a separate credentials section rather than combining with the environment section...need to think on this.