Re: Moving Diego Repositories

Will Pragnell <wpragnell@...>

Have we abandoned plans for the import path service Eric proposed back in
April? If not, aren't we just going to have to update all our imports again
once that rolls out?

On 25 June 2016 at 18:36, Kris Hicks <khicks(a)> wrote:

I've found when doing this the easiest thing to do is to use sed to remove
existing imports followed by goimports -w on the same files.


On Sunday, June 26, 2016, Amit Gupta <agupta(a)> wrote:

Congrats on making it official!

I assume you folks are going to build some scripts or some "go fmt -r" to
find/change all import paths that need updating. If you find anything
useful that other teams might be able to leverage, sharing would be much


On Fri, Jun 24, 2016 at 4:20 PM, Onsi Fakhouri <ofakhouri(a)>

That stuff has always technically been foundation code and should have
moved out of pivotal-golang into cloudfoundry-incubator long ago. Back
when we made the org the rules about how orgs are structured weren't quite
so clear.


On Fri, Jun 24, 2016 at 4:18 PM, Alex Suraci <asuraci(a)> wrote:

why are we moving the pivotal-golang repos? I thought the point of that
was to be able to create those cheaply for super generic packages that we
just need to have somewhere in cases where the repo incubation foundation
lifecycle crap gets in the way. are we now able to create repos willy-nilly
under the cloudfoundry org?

On Sat, Jun 25, 2016, 6:13 AM James Myers <jmyers(a)> wrote:

Hi all,

We are currently in the process of moving all of the Diego
repositories from `cloudfoundry-incubator` to the `cloudfoundry`

Specifically we are moving the following repositories to the
`cloudfoundry` organization:

- auction
- auctioneer
- bbs
- benchmark-bbs
- buildpack_app_lifecycle
- cacheddownloader
- cf-debug-server
- cf-lager
- cf_http
- consuladapter
- converger
- diego-ssh
- diego-upgrade-stability-tests
- docker_app_lifecycle
- executor
- file-server
- healthcheck
- inigo
- locket
- rep
- route-emitter
- runtime-schema
- vizzini
- diego-cf-compatibility
- diego-ci-pools
- diego-ci
- diego-design-notes
- diego-dev-notes
- diego-dockerfiles
- diego-perf-release
- diego-release
- diego-stress-tests

We are also moving the following from `pivotal-golang` to
`cloudfoundry` as well:

- archiver
- bytefmt
- clock
- eventhub
- lager
- localip
- operationq

We are also renaming the following, and will be updating their package
names accordingly:

- benchmark-bbs -> benchmarkbbs
- buildpack_app_lifecycle -> buildpackapplifecycle
- cf-debug-server -> debugserver
- cf-lager -> cflager
- cf_http -> cfhttp
- docker_app_lifecycle -> dockerapplifecycle
- file-server -> fileserver
- runtime-schema -> runtimeschema

You might be asking yourself, what does this mean for me?

Generally it means the following:

- If you are importing any of the above repos in your golang code, you
should change it from ``
<> to ``

- Update your golang code when you update your dependencies to
reference the new package names marked above.

- If you are consuming the Diego bosh release from, you will
need to update the location to

Other than that, github redirects should handle most of the issues for

As a side note we are also moving the following deprecated
repositories to the `cloudfoundry-attic`:

- diego-acceptance-tests
- diego-smoke-tests
- receptor
- runtime-metrics-server

Let us know if you have any questions.


Jim + Andrew, CF Diego Team

Join { to automatically receive all group messages.