Hey peeps, quick question on exporting resource. I am trying to export CustomResource from one stack to another for the purpose of using its data in the construction of another CustomResource. So; Stack1 has Res1, I would like to export it, but it remains managed in stack 1 Stack2, import Res1 as it is needed to construct Res2 I know i can export/import string, but what i would like is for Res1 to be a "Res1" in Stack2, not a json payload of metadata to keep the code dealing with resource object in a ubiquitous fashion. is there an easy way to that. I find my self having some issue reconstructing the object. Thanks!

Check out this page and see if it's what you're looking for https://www.pulumi.com/learn/building-with-pulumi/stack-references/

Thank, yes I have, but this only deals with string. Which is pretty trivial to do. What I am looking for more for something like

pulumi.export("myBucket", a_bucket)

and then import that into another stack as a aws.s3.Bucket so I can use the object in the creation of other resource

While you can output then entire JSON for an object, you might be better off using strings with getters in your other plan. e.g.

const sharedStack = new pulumi.StackReference("my/stack/reference");
const logBucketId = sharedStack.getOutput("logBucketId");

const logBucket = aws.s3.Bucket.get("log-bucket", logBucketId)

got it, so there is no "official way" to import a managed Resource. I can appreciate the difficulty of management ownership. I did try to use the

get

feature of CustomResource, by only exporting the minimum info for a remote lookup, but given that one deals in

Output

and the

get

seems to be "right now" I seem to have hit a bit of a wall

Your custom resource definition should probably be in a package that you can install across both stacks, then passing references and reconstructing the resource component may feel more natural.

interesting, is there an example of that somewhere i could read, or what part of the doc would lead me to that approach?

Here's a blog post about the concept at a high-level. https://www.pulumi.com/blog/creating-and-reusing-cloud-components-using-package-managers/

interesting, thank you, I may have to rewrite some stuff after reading, kicking my self for not having found this sooner 😄

Hey, it happens, and Pulumi is pretty new, best practices are still emerging.

Here's a blog post about the concept at a high-level.

upon closer inspection, I am doing a version of this, but mostly for already constructed Resource to keep import and export as programmatic as I can (no hard-coded resource name or offband knowledge) to use resource from another stack as information.