Rename 'optional' ops manager

[acrmp]

Operators can currently choose to stand up a second 'optional' Ops Manager instance:

https://github.com/pivotal-cf/terraforming-gcp/blob/eca95728e665c64703eb7c5806d41c6dbdc00f21/dns.tf#L18

On our team we've typically used this instance for testing upgrade scenarios:

1. An existing installation is exported from the older 'optional' ops manager instance
2. The installation is imported into the normal ops manager instance to test the upgrade

Because it better reflects our usage we'd prefer to rename the 'optional' instance to something like 'initial'.

However maybe other folks out there are using the optional Ops Manager for some other purpose in which case the name change may not make sense. Please leave a comment on this issue to share with us how you are using the optional opsman.

Thanks,

Andrew.

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

[genevieve]

Do you want to make this a var that defaults to pcf-optional but we can overwrite to initial using the var?