Writing a provider that depends on another provider

I might be missing something, but I haven’t been able to figure out from documentation what the right way to depend on providers would be when writing a provider myself. I found this docs page which makes it clear what not to do but I’m less clear on what to do.

To provide a little more clarity on what I’m trying to do - I want to experiment with a kind of “meta-provider” that provides a simpler surface area for complex underlying resources . Basically imagine a provider that will expose a schema which is then transformed in non-trivial ways into the schemas of a number of underlying resources (from publicly available providers) that need to be provisioned.

Any tips on how I might go about this?

That’s a tricky one we don’t really have any good patterns for at the moment. It’s tempting to say you should import the provider you’re wrapping, but most aren’t written to be importable–what they export isn’t designed with an eye for consumers, and their versioning doesn’t reflect that API surface.

I think a fork is the best suggestion I can offer, unfortunately.