itowlson

> Would it be possible to change the definitions of triggers to include a set of target world names and versions? I'm not sure what you're envisaging. Are you suggesting...

> Can you say more about why that's not cacheable? Sorry, it _is_ cacheable and indeed cached, but it is cached by digest. So until we know the digest... >...

> I had always assumed that we'd support fetching target world definitions from more than a single place I feel like we've had a lot of design discussions before and...

> > Would it be possible to change the definitions of triggers to include a set of target world names and versions? > > I'm not sure what you're envisaging....

> To the particular point of target worlds: I don't see how we could centralize them without also centralizing trigger plugins, which doesn't seem desirable. Centralisation would be undesirable for...

I believe we do do the digest check at `spin up`. Although I haven't read that code for a while so I may be misunderstanding / misremembering!

So this takes us back into "what is `spin build`" territory. There is certainly scope in the `spin up --build` and `spin watch` cases (we may need to do some...

It occurs to me that the long ramble above also ties in with some of the discussion/concerns around the multiple build profiles SIP.

Okay, on the subject of centralising and decentralising and getting WITs from different sources: My original stab at this (okay, _one_ of my original stabs at this) was that an...

I had a long chat with @tschneidereit about this and I am going to rework it based on: * We will backtrack on representing environments as WIT packages, and instead...