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

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

Excellent!!!. Good luck.

Installed the sample app and tried it on Bluemix and I don't see CF_INSTANCE_GUID or INSTANCE_GUID in Environment section. How do I know if its Diego or DEA ?. Thanks, Vinod

You can use xip.io for temporary domain, try generating manifest again and deploy.

That was the problem. I removed the MySQL profile and it worked. Thanks!

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

As I was not planning on sigining exposing this deployment to the outside, I was planning on using HAPROXY through it's floating IP. I did not set a domain, because I have not yet interfaced with my

Hello Eyal, Can you paste the domain properties from your final manifest ( system domain & app domain part). Thanks Ronak

I know there are some changes to the env variables between DEAs and Diego. I don't know exactly and don't have a DEA to

Hi all, We are currently in the process of moving all of the Diego repositories from `cloudfoundry-incubator` to the `cloudfoundry` organization. Specifically we are moving the following

Hello Amit, I have removed the lines that you have marked. Now I am getting a different error... Process 'consul_agent' running Process 'cloud_controller_ng' Connection

ok thanks, will wait for someone to reply. Do you know if the behavior should be same or has it been changed from DEA to Diego ?. Thanks, Vinod

Yes sir, please try removing them and regenerating your manifest before redeploying. Cheers, Amit

Hello Amit, I used the latest stub from GIT. As I was working last week, I could swear I saw the stub change as I was working... I guess that that explains it. Should I remove the lines in the

Hi Bryan, UAA needs a database to store user accounts. By default it uses in-memory db, In your case, it is trying to connect MySQL DB. I am not sure. How are you running you UAA server? Are you

Those stubs are out of date. Our OpenStack stubs may remain out of date for a bit while we find more resource to support automated testing of the stubs against and OpenStack environment. In the mean

Hi Amit, We have the exact same issue and our cf-stub looking exactly like the one u pointed out. Stuck with this issue, Regards, Pramod

Hi Eyal, No need to tear things down. By any chance, did you generate your manifest using a stub? Do you have something that looks like this in your

Hi there!  We found that if you monit stop all the consul nodes before upgrading and adding ssl. The deployment should upgrade without any issues. Thanks, Long