On 13 May 2019, Acquia will release a change to Acquia Cloud Pipelines, which may require a change to your
Acquia is changing the way that Acquia Pipelines handles
pipelines-deploy commands nested within a build event. The current configuration is not in line with best practices and can cause builds to fail for some customers. To encourage best practices and to prevent builds from failing, Acquia Pipelines will no longer support the current configuration. If this is detected, builds will fail.
In preparation for this change, customers should review their
acquia-pipelines.yml file to check for this condition. If a
pipelines-deploy command is present, it is recommended that you move the command from within the build event to the
Below is an example of a
pipelines-deploy command nested within the build event:
events: build: ... steps: - deploy: script: - pipelines-deploy
This should be updated so the
pipelines-deploy is moved outside of the build event and into the
events: ... post-deploy: steps: - deploy: script: - pipelines-deploy
Once this change is implemented, no further action is required, and your builds will continue to deploy as normal.
For customers using Acquia BLT, this change will be included in the acquia-pipelines.yml file in the latest release, which can be found here.