This message was deleted.

as far as I know, no, you have to use

extendsFrom(fooConfiguration.get())

https://github.com/gradle/gradle/issues/26732 In theory you could use a detached configuration, but they aren't compatible with extendsFrom https://github.com/gradle/gradle/issues/6881

You don't really break configuration avoidance anyway. While it does not hurt to always use the lazy APIs where possible in case something changes in the future, most containers are not treated lazily anyway. The most prominent example that is, is the tasks container and for tasks you should take care to always stay lazy. But with configurations you do not really win much with jumping through hoops just to not eagerly access them.