search

cloudfoundry-community / cf-resource

Concourse resource for interacting with Cloud Foundry
Apache License 2.0
35 stars 63 forks source link

Specify app route in concourse job params #27

Closed dannysullivan closed 7 years ago

dannysullivan commented 7 years ago

We're trying to blue-green deploy an app to multiple environments with different routes and environment variables in each environment. The only thing preventing us from using the cf-resource is the lack of support for specifying routes in the concourse job. As is, we can use different manifests for each environment, but it seems like overkill since there's only one difference between the environments (the route).

Looking at the code, it seems like this would involve adding an AddRoute method to https://github.com/concourse/cf-resource/blob/master/out/manifest.go . I'd be happy to submit a pull request if you think this idea makes sense.

concourse-bot commented 7 years ago

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

CAFxX commented 7 years ago

We have the same problem (for both routes and stack)

benmoss commented 7 years ago

This would be great, we are also trying to push an app to multiple spaces and having route conflicts

chendrix commented 7 years ago

I would look at a PR for this, but in general I don't think asking people to change their manifest via tasks is too big of an ask.

This could obviously end up in a combinatorial explosion where "my manifests are the same except for X parameter", and we end up in the same place as the old version of this resource that specified every parameter independently.