No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

found this thread on github <https://github.com/pulumi/pulumi/issues/1641>
<https://github.com/pulumi/pulumi/issues/3635>

<@U02PF9MP1QD> I think you're talking about ComponentResources:
<https://github.com/pulumi/examples/blob/258d3bad0a00020704743e37911c51be63c06bb4/gcp-py-network-component/network.py>

<https://github.com/pulumi/examples/blob/258d3bad0a00020704743e37911c51be63c06bb4/gcp-py-network-component/__main__.py#L12-L15>

yes, in this example `config` locates in the same folder as `___main___`
in my case I’m trying to import package from level above
typically you can do relative import like `from ..models import ModelItem` , but with pulumi it doesn’t work

the idea to share models between pulumi and application code

If it helps; the only workaround I found was to use the `sys.path.append` trick:
```sys.path.append(os.fsdecode(Path(__file__).resolve().parent.parent.parent))
from path.to.whatever import *```

I found through trial and error that this only works if you use `__main__` for the main Pulumi module, if you override it in config then it doesn’t work.  It also only works with the `from x import y` form of import

I recall seeing a GH issue and a link to a sample repo as well, I don’t have the link to hand (oh, the example workaround is linked to the above GH issue, if you click through enough links!  <https://github.com/followben/pulumi-example/blob/master/src/infra/project2/__main__.py#L12>)

I suggest upvoting <https://github.com/pulumi/pulumi/issues/7360> as this is something that could really use improvement