task failure import-opsmgr-settings about pcf-pipelines HOT 5 CLOSED

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.

from pcf-pipelines.

Note that this is the same bug as is PR'd in #376.

from pcf-pipelines.

This is not the same issue as the PR #376.
The proposed solution in the PR will not work for the version of om that is currently installed on the docker image.

The issue that this person is experiencing is an issue with om.
It has a second issue reported on om.

from pcf-pipelines.

The change that needs to be made to the task.

@@ -31,8 +31,8 @@ function main() {
       --skip-ssl-validation \
       --request-timeout 86400 \
       import-installation \
-      --installation "${cwd}/opsmgr-settings/${OPSMAN_SETTINGS_FILENAME}" \
-      --decryption-passphrase "${OPSMAN_PASSPHRASE}"
+      --decryption-passphrase "${OPSMAN_PASSPHRASE}" \
+      --installation "${cwd}/opsmgr-settings/${OPSMAN_SETTINGS_FILENAME}"
  }

  main "${PWD}"

from pcf-pipelines.

This is being fixed because this is a breaking change for current pipelines.

This will be included in the next (last) release of pcf-pipelines. This feature has not been tested by CI, nor will it be. Use this commit and the corresponding release at your own risk.

In the future, please use platform-automation for all your automation needs. Pivotal Documentation

from pcf-pipelines.