yes. I think I have. But I can't share it 😞

fair enough. Can I ask how you got around the error

pants.core.goals.export.ExportError: No resolve named {resolve} found in [python].resolves.

? I think it's because all resolve names get passed to all resolve classes, which doesn't work because I'm requesting a Terraform resolve but Python is attempting to consume it.

that does seem broken. by the look of it, you'd have to disable the python backend when exporting for resolves/targets from other backends..

no. Had a look no I did not build a

export

goal rule. I did build a

export-a-thing

goal tho. Maybe for the same reason? It's been a while.

hehe, that makes sense. I think, then, I'll leverage the same machinery as lockfiles uses to convert a name into a lockfile associated with a language. From there, pants will automatically dispatch the per-language request to the right codepath. I think we might also get the ability to export internal tools for free from that.