search

cloudfoundry-attic / cf-deployment-transition

This repository is deprecated - no longer accepting PR's or Issues
Apache License 2.0
9 stars 5 forks source link

Drop remove of cni job now that it's unused upstream. #9

Closed jmcarp closed 6 years ago

jmcarp commented 6 years ago

We're still using a few opsfiles in this repo, including remove-cf-networking-for-transition.yml. As of cf-deployment 2.0, a few jobs in diego-cell got renamed. This patch updates the cf networking opsfile with the latest names. Hopefully we'll get around to enabling cf networking soon and not need this opsfile anymore 🤞

cfdreddbot commented 6 years ago

Hey jmcarp!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

cf-gitbot commented 6 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/158465454

The labels on this github issue will be updated when the story is started.

jmcarp commented 6 years ago

cc @dsabeti

heyjcollins commented 6 years ago

Hi @jmcarp - the RelInt team is not testing cf-deployment-transition beyond the transition matrix it supported when we made the initial cutover to cf-deployment.

As a result, we can't accept PR's to this repo. We recommend using the transiton matrix to transition from cf-release to a supported cf-deployment and from there, you can use cf-deployment to upgrade to 2.0.