Feature request to specify products during apply-changes

[Houlistonm]

URL or GitHub link to the page where you're having the issue

Is your request for a change or addition to content related to a problem? If so, please describe.
Feature Request.

Describe the solution you'd like
Updates to the apply-changes task to allow a pipeline developer to override the default (all) products that changes are applied.

Describe alternatives you've considered
None

[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.

[jtarchie]

There is a historical context of why the team chose to not allow this. We did not have guarantees that the Apply Changes would be idempotent with only specifying single products. From the end-user it is faster, but there were too many edge cases of "if something didn't fully install".

[Houlistonm]

@jtarchie I understand your comments, but our specific use case is for the credhub service broker tile that doesn't deploy any VMs. The CSB tile deploys an application in the post-deploy errand. We'd like to deploy this snowflake separate from other deployments.

[anEXPer]

https://docs.pivotal.io/platform-automation/v5.0/tasks.html#stage-configure-apply allows this by wrapping other cheap, idempotent tasks to the front of the apply for reliability/consistency purposes. While it should be referenced from the Apply Changes task description so as to be more discoverable, I see it currently isn't. Does that task do what you need, or is there some mismatch for your situation there?