-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: support ops-files from multiple repositories in bosh-deploy #2
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/139854967 The labels on this github issue will be updated when the story is started. |
@aashah Yeah, this one is hard, because concourse doesn't support making tasks with a variable number of arguments. One thing we talked about shipping was a task that copies ops files into a centralized location. So imagine that you had the
The task would be REALLY simple (probably just a Let me know if this would satisfy your use case. I'll also wait to see if other teams need something like this as well. In the meantime, I can try to poke the concourse team for help. |
I think ticket can be closed. You can specify
according to this |
Hey @medvedzver, That only works for files that are in the same |
My bad. You are right. |
Hey @aashah and @medvedzver, take a look at this new task. This should allow you to "collect" all of your ops-files into a single directory so that your I'm going to close the issue, but feel free to reopen it if you have other questions. |
Not sure whether concourse will fully be able to support this, but it'd be nice to allow teams to have their own ops files. Currently, in order to write our own, we had to "vendor" the ops-files in
cf-deployment
.The text was updated successfully, but these errors were encountered: