Secrets with drone exec

Drone Support
1

Picking up drone for the first time in a while, using 1.0. Is it still just setting your secrets as env vars? Seems to not be working.

Env var:

➜  hello-httpd env | grep CHEF_KEY
CHEF_KEY=thekey

.drone.yml

kind: pipeline
name: build
steps:
  - name: build
    image: ubuntu
    environment:
      CHEF_KEY:
        from_secret: CHEF_KEY
    commands:
      - echo "$CHEF_KEY"

Outputs:

[build:0] + echo "$CHEF_KEY"
[build:1]
2

If you are using the 1.0 CLI you need to pass secrets to the CLI from file.

example command:

drone exec --secret-file=secets.txt

example file:

CHEF_KEY=thekey
3

10-4 thanks Brad!

(any why are you working on the long weekend??)

4

one could ask you the same question :slight_smile:

hope all is well

5

On a new team, trying to evict an entrenched Jenkins…

As a bit of a feature request, could you strip off leading export when parsing that file? I’ve got a habbit of doing stuff like source ~/bad_idea/aws_creds.sh when working locally and I could re-use those files if you stripped the leading export. #twocents anyway

6

I believe this is supported. We use joho/godotenv to parse the file which claims to support a variety of bash-like formats, for example:

# I am a comment and that is OK
SOME_VAR=someval
FOO=BAR # comments at line end are OK too
export BAR=BAZ