Chris Townsend
Chris Townsend
> Sounds like a workable solution, then? Hmm, now that I think about it, I did get an email about testing the forward, but you said in the email that...
Hrmph, no, I didn't :slightly_frowning_face:
Hey @Saviq! The lack of getting the failure email is not dependent on this PR, right?
Ok, what I meant was is fixing the lack of notifications something we do in this PR or is it somewhere else that it needs fixed?
> Can't you instead maintain backwards compatibility? Sure, it's *possible*, but it would add lots of complexity for Blueprints maintainers and for Multipass. The notion of Blueprint-specific images will *only*...
Maybe restricting the v2 Blueprints to just amd64 and arm64 is not necessary although we did some analysis and this affects only Linux and only 0.5% of those users are...
> Right, that's the backwards compatibility I had in mind. Just clarify one thing for me - can you still use image aliases in `v2`? There really shouldn't be a...
I certainly understand your point and thought about this too. It's not just about the `images` grammar- that's actually the uncomplicated part. The complicated part is the handling of the...
> I suppose I just dislike the inevitable duplication I don't really like it either, but I think the alternative of having a complicated Blueprint is worse, but yes, I...
Hi @boursawb! That `cloud-init` file looks valid, so I'm wondering which directory you have the `test-cloud-config.yaml`. If it's not in your user's home directory, snap confinement will deny access to...