Closed poy closed 5 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/154735316
The labels on this github issue will be updated when the story is started.
Hey @apoydence. We have a much less intelligent task in our runtime-ci repo that uploads a stemcell from a local file, as opposed to constructing a bosh.io url for downloading/uploading the stemcell.
We originally did this because bosh.io was not hosting windows stemcells at the time; even still, it only supports GCP, AWS, and Azure, while our task offers support for bosh-lite and vSphere as well. I'll use the Github issue as a story to investigate what it would take to update the task to support windows cells as well.
I have reached into runtime-ci for your upload task for windows. I put a comment on what appears to be the tracker story associated with this issue (though that linkage is broken from the tracker side, maybe?) but I figured I'd come by here and mark my need, too.
Is this still relevant ? The diego team started using bosh-upload-stemcells task and we haven't noticed anything wrong with the task so far. This could be due to the fact that the stemcell is already present on the director.
I'd consider this done - the upload-stemcells task works explicitly for this, as long as you provide an ops file that adds the windows stemcell.
Which is good, because RelInt deleted the task I was using in runtime-ci. (Which is further proof that this need has been met elsewhere.)
I'm going to close it. If we bump into issues down the road I'll reopen it.
We have an environment that requires a windows diego cell, however the bosh-upload-stemcell-from-cf-deployment/task does not upload the windows stemcell.
Is there a way to get around this that doesn't involve uploading it manually each time there is an updated stemcell?