Martin Smith

Just ran into this too -- it'd be nice to know controls aren't optional, when the examples omit it.

Something to limit the impact to Berkshelf of having many, many old releases all still available in Supermarket would be awesome. :+1:

> You might mark a cookbook so that it will not depsolve and be offered in the universe but it must still download to not break existing Berksfile.locks. This would...

I think there are two issues at play here. Regarding the impact to berkshelf, I've seen a number of circumstances where removing a cookbook from Supermarket and reuploading only the...

Well, the berkshelf issue aside, I'd argue there's still a case for yanking, for the pathological case. > And I think you don't appreciate the impact if someone has a...

Hi @nellshamrell! > if the pull request currently in knife supermarket is insufficient Do you have a link to that PR? > Potential Solution: ... :+1: I think your items...

> The warning should clearly state that it will break anyone's production deployments who has that version in a Berksfile.lock, pinned in an environment file, or used in a compiled...

:+1: I had suggested in a previous thread that even just a way to hide it would work for me. I can see that some others still might want to...

I'd be interested in this too -- CC @lnxchk in case you know of any good best practices here. The current UX is so difficult; we end up either doing...

@lnxchk It's more of a UX thing than actual bugs. From what I've seen, either with a significantly old start/rotation_virtual_start, or if even a schedule has been opened and saved...