Comment 1 for bug 1708541

This is unviable without making significant changes to the way bootstrap works. The client code currently knows how to create the bootstrap instance, and works in concert with the exact same agent version on it.

We would need to either introduce cross-version compatibility between client/server bootstrap procedures (which I think would be too costly in terms of maintenance, and therefore a mistake); or we could split the client-side bootstrap code into a separate binary, and have the client fetch the appropriate version from streams.canonical.com. I think the latter would be very reasonable, and probably better than what we have today.

Marking this as Wishlist for now, since it's an improvement over an existing solution.