Skip to content
master
Switch branches/tags
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
cli
 
 
db
 
 
 
 
 
 
 
 
 
 
 
 
 
 

GoCD File Based Secrets Plugin

This is a file based secrets plugin which implements the GoCD Secret Plugin endpoint. This plugin allows retrieving of secrets that are stored in encrypted files.

For comprehensive details about Secret Management in GoCD please refer to the documentation.

Building the code base

To build the jar, run ./gradlew clean test assemble

Installation

  • This plugin comes bundled along with the GoCD server, hence a separate installation is not required.
  • GoCD introduced support for Secrets Management in v19.6.0, in order to use this plugin your GoCD version should >= 19.6.0.

Usage instructions

  1. Download the plugin jar from the GitHub Releases page
  2. Execute the init command to initialize the secret database. Although it's optional but it is recommended to store your secret file under CONFIG_DIR. Doing this will make secrets database file part of the backup process. The CONFIG_DIR is typically /etc/go on Linux and C:\Program Files\Go Server\config on Windows.
java -jar gocd-file-based-secrets-plugin-$VERSION$.jar init -f secrets.json
  1. Add/Update a secret:
java -jar gocd-file-based-secrets-plugin-$VERSION$.jar add -f secrets.json -n my-password -v
  1. Show the value of the secret:
java -jar gocd-file-based-secrets-plugin-$VERSION$.jar show -f secrets.json -n my-password
  1. Show all secret keys:
java -jar gocd-file-based-secrets-plugin-$VERSION$.jar keys -f secrets.json
  1. Remove a secret:
java -jar gocd-file-based-secrets-plugin-$VERSION$.jar remove -f secrets.json -n my-password

Configuration

The plugin needs to be configured to use the secrets database file.

The configuration can be added directly to the config.xml using the <secretConfig> configuration.

  • Example Configuration

    <secretConfigs>
      <secretConfig id="Env1Secrets" pluginId="cd.go.secrets.file-based-plugin">
          <description>All secrets for env1</description>
           <configuration>
              <property>
                  <key>SecretsFilePath</key>
                  <value>/godata/config/secrets.json</value>
              </property>
          </configuration>
          <rules>
              <allow action="refer" type="environment">env_*</allow>
              <deny action="refer" type="pipeline_group">my_group</deny>
              <allow action="refer" type="pipeline_group">other_group</allow>
          </rules>
      </secretConfig>
    </secretConfigs>

    <rules> tag defines where this secretConfig is allowed/denied to be referred. For more details about rules and examples refer the GoCD Secret Management documentation

  • The plugin can also be configured to use multiple secret database files if required:

    <secretConfigs>
      <secretConfig id="Env1Secrets" pluginId="cd.go.secrets.file-based-plugin">
          <description>All secrets for env1</description>
           <configuration>
              <property>
                  <key>SecretsFilePath</key>
                  <value>/godata/config/secrets.json</value>
              </property>
          </configuration>
          <rules>
              <allow action="refer" type="environment">env_*</allow>
              <deny action="refer" type="pipeline_group">my_group</deny>
              <allow action="refer" type="pipeline_group">other_group</allow>
          </rules>
      </secretConfig>
      <secretConfig id="Env2Secrets" pluginId="cd.go.secrets.file-based-plugin">
          <description>All secrets for env1</description>
           <configuration>
              <property>
                  <key>SecretsFilePath</key>
                  <value>/godata/config/secrets_env2.json</value>
              </property>
          </configuration>
          <rules>
              <allow action="refer" type="environment">env_*</allow>
              <deny action="refer" type="pipeline_group">my_group</deny>
              <allow action="refer" type="pipeline_group">other_group</allow>
          </rules>
      </secretConfig>
    </secretConfigs>

A secret file is made of JSON, and has the following data structure:

{
  "secret_key": "...",
  "secrets": {
    "my-password": "AES:..."
  }
}

The secret defined in the above example can be used by defining a Secret Param with syntax: {{SECRET:[Env1Secrets][my-password]}} in entities which support secrets. For more information about supported entities refer the Secrets Management documentation.

Troubleshooting

Verify Connection

For a given secret config verify if the file database can be accessed by the plugin. The Secrets Configuration page under Admin > Security gives an option to verify connection.

Enable Debug Logs

Edit the file wrapper-properties.conf on your GoCD server and add the following options. The location of the wrapper-properties.conf can be found in the installation documentation of the GoCD server.

# We recommend that you begin with the index `100` and increment the index for each system property
wrapper.java.additional.100=-Dplugin.cd.go.secrets.file-based-plugin.log.level=debug

If you're running with GoCD server 19.6 and above on docker using one of the supported GoCD server images, set the environment variable GOCD_SERVER_JVM_OPTIONS:

docker run -e "GOCD_SERVER_JVM_OPTIONS=-Dplugin.cd.go.secrets.file-based-plugin.log.level=debug" ...

License

Copyright 2019 ThoughtWorks, Inc.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.