Can we removed all devel agents from released streams.

[Ian Booth]

On 14/11/14 06:28, Curtis Hovey-Canonical wrote:
> We have another cases where an env using --upload-tools tried to
> upgrade from 1.18.4 to 1.20.x and got 1.19.x. I want to remove all the
> devel agents from the released streams.
> 
> We have already created separate streams for devel and proposed agents
> to ensure environments cannot upgrade to them without explicitly set
> the environment to use them.
> 
> I want to ensure we don't have old devel agents in our released
> streams. This will prevent anyone from getting these version from our
> official locations. This may also prevent environments that are idling
> on obsolete version from deploying more units.
> 
> Are there other issues that will happen if I remove the devel agents?
> Is this a bad and dangerous idea?
> 

I think this is a good idea and can only see benefits.
So +1 from me.

Having said that, if they used upload-tools then the public metadata is not used
anyway. Juju will generate metadata for the jujud it finds in the user's path
(or compiles from source if no jujud is found). The metadata is written to their
environ storage (for Juju < 1.21). Do we have any more information about their
setup? It would be interesting to understand what happened.