--decryption-passphrase location chance

[sapient007]

--decryption-passphrase needs to be set before import-installation for om to work.

Usage: om [options] import-installation [<args>]
  --client-id, -c, OM_CLIENT_ID                          string  Client ID for the Ops Manager VM (not required for unauthenticated commands)
  --client-secret, -s, OM_CLIENT_SECRET                  string  Client Secret for the Ops Manager VM (not required for unauthenticated commands)
  --connect-timeout, -o                                  int     timeout in seconds to make TCP connections (default: 5)
  --decryption-passphrase, -d, OM_DECRYPTION_PASSPHRASE  string  Passphrase to decrypt the installation if the Ops Manager VM has been rebooted (optional for most commands)
  --env, -e                                              string  env file with login credentials
  --help, -h                                             bool    prints this usage information (default: false)
  --password, -p, OM_PASSWORD                            string  admin password for the Ops Manager VM (not required for unauthenticated commands)
  --request-timeout, -r                                  int     timeout in seconds for HTTP requests to Ops Manager (default: 1800)
  --skip-ssl-validation, -k                              bool    skip ssl certificate validation during http requests (default: false)
  --target, -t, OM_TARGET                                string  location of the Ops Manager VM
  --trace, -tr                                           bool    prints HTTP requests and response payloads
  --username, -u, OM_USERNAME                            string  admin username for the Ops Manager VM (not required for unauthenticated commands)
  --version, -v                                          bool    prints the om release version (default: false)

Command Arguments:
  --config, -c             string             path to yml file for configuration (keys must match the following command line flags)
  --installation, -i       string (required)  path to installation.
  --polling-interval, -pi  int                interval (in seconds) at which to print status (default: 1)```

Thanks for submitting an pull request to pcf-pipelines.

To speed up the process of reviewing your pull request please provide us with:

* A short explanation of the proposed change:

* An explanation of the use cases your change solves:

* Expected result after the change:

* Current result before the change:

* Links to any other associated PRs or issues:

* [ ] I have viewed signed and have submitted the Contributor License Agreement

* [ ] I have made this pull request to the `master` branch

* [ ] I have run all the unit tests 

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[kcboyle]

@sapient007 are you using the Dockerfile for pcf-pipelines? The --decryption-passphrase flag is only supported in very very new versions of om, and pcf-pipelines is not supported on these newer versions. pcf-pipelines might be updated to 0.42.0 in the near future, given passing tests on our end. e

[tichimura-pivotal]

@kcboyle I also faced same situation, and the task.sh is called that flag.
https://github.com/pivotal-cf/pcf-pipelines/blob/v0.23.12/tasks/import-opsmgr-settings/task.sh#L35