Been thinking, x-incus-* will be all optional. With them you will be able to create other types of nics than just bridge or use other pools than just the default it creates.
.env limits us to strings that brings complications.
Thining about a companion compose.incus.yaml that you might create next to a comose.yaml, that might be easy to implement or just works out-of-the-box with compose-go.
yeah, that sounds good. I would probably name it incus-compose.<ext> to go with the naming scheme, but that’s just bike shedding.
.incus.yaml is a profile for compose with a little trickery auto loaded by compose-go and ignored by docker-compose 
EDIT: It should be able to load other profiles as well.
@Sagi - Pushed the major update.
The refactor is done. Extensible client library, hooks for everything, ~70% test coverage on the core package. KISS and boring.
Your reported bugs should be gone - if you’re still testing, would appreciate verification.
Next is implementing the docker-compose commands.
Also it moved: René Jochum / incus-compose · GitLab
Chiming in here to share the AUR package I’ve created for incus-compose. Comments/suggestions welcome 
(I also created an issue in the repo before thinking of announcing it here instead)
Cheers