-
Notifications
You must be signed in to change notification settings - Fork 282
Matrix compatibility automation #387
Comments
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. |
pcf-pipelines is deprecated, and will be archived before the end of April. The replacement will be the Pivotal product platform automation docs.pivotal.io/platform-automation. It is built primarily on |
Hi @kcboyle
But I saw too on the website you can create your director into a docker directly. Regards, |
Platform Automation can absolutely be used to deploy new Ops Managers, yes. The Unlike pcf-pipelines, with Platform Automation you need to build out your pipeline yourself. http://docs.pivotal.io/platform-automation/v2.1/reference/pipeline.html#installing-ops-manager-and-tiles (Line 199+) gives an example of how you can use the Another difference is that Platform Automation does not maintain terraform templates. We recommend using the terraforming-* repos that the Pivotal infrastructure team manages. These repos are actively updated, and eliminates the problem of out of date templates in pcf-pipelines. To use these repos, it requires you to maintain your own override.tf for the pieces you cannot consume. |
Question
Hi, we use pcf-pipelines to deploy or new sandbox and others env. Some time we got the matrix version problem between stemcell, ert, etc... Shame on us we didn't checked that.
We want to automate and continue to skip that check in our mind.
Possible Fix
Is it possible to add the matrix versions into a file and catch it in the pipeline to set the value with that ?
Regards,
Hk
The text was updated successfully, but these errors were encountered: