emccode / rexray / 162

162

Pull #100

travis-ci

akutz 
Config Data is Now Secure & Plain-Text

The configuration data in REX-Ray is now stored separately as secure &
plain-text. The plain-text version of the data is serialized and sent
to the server when necessary to provide credentials. However, when
executing commands like `rexray service module types`, the produced
output will be secure by default and no longer include the following
configuration keys:

  * AwsSecretKey
  * RackspacePassword
  * ScaleIoPassword
  * XtremIoPassword

For example:

    [0]akutz@poppy:rexray$ rexray service module types
    [
      {
        "id": 1,
        "name": "AdminModule",
        "defaultConfigs": [
          {
            "address": "tcp://:7979"
          }
        ]
      },
      {
        "id": 2,
        "name": "DockerRemoteVolumeDriverModule",
        "defaultConfigs": [
          {
            "address": "unix:///run/docker/plugins/rexray-remote.sock",
            "config": {
              "LogLevel": "info",
              "StorageDrivers": [],
              "VolumeDrivers": [
                "docker"
              ],
              "OsDrivers": [
                "linux"
              ],
              "MinVolSize": 0,
              "RemoteManagement": false,
              "DockerVolumeType": "",
              "DockerIops": 0,
              "DockerSize": 0,
              "DockerAvailabilityZone": "",
              "AwsAccessKey": "",
              "AwsRegion": "",
              "RackspaceAuthUrl": "",
              "RackspaceUserId": "",
              "RackspaceUserName": "",
              "RackspaceTenantId": "",
              "RackspaceTenantName": "",
              "RackspaceDomainId": "",
              "RackspaceDomainName": "",
              "ScaleIoEndpoint": "",
              "ScaleIoInsecure": false,
              "ScaleIoUseCerts": true,
              "ScaleIoUserName": "",
              "ScaleIoSystemId": "",
              "ScaleIoSystemName": "",
              "ScaleIoProtectionDomainId": "",
   ... (continued)
Pull Request #100: Config Data is Now Secure & Plain-Text

344 of 2900 relevant lines covered (11.86%)

0.12 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

67.2
/config/config.go


Build SHA Not Found

The commit SHA "07274005ca46759da8d1095ac04c50a6e7eafee0" was not found in your repository, so the file cannot be loaded. This may be because you posted from a local development environment, or your CI created an ephemeral commit.