Currently the docs explain how to use the pulumistateapi provider to access attributes from resources in a Pulumi stack. This is great, but not what most users will want to do, since reaching into particular resources and grabbing their attributes isn't stable compared to using values that have been explicitly exported by calling pulumi.export, i.e. the Pulumi stack output. Fortunately the Pulumi API exposes the Pulumi stack output as a resource in the stack, so we can access it using the resource type pulumi_pulumi_Stack as now explained in README.md.
Currently the docs explain how to use the
pulumistateapiprovider to access attributes from resources in a Pulumi stack. This is great, but not what most users will want to do, since reaching into particular resources and grabbing their attributes isn't stable compared to using values that have been explicitly exported by callingpulumi.export, i.e. the Pulumi stack output. Fortunately the Pulumi API exposes the Pulumi stack output as a resource in the stack, so we can access it using the resource typepulumi_pulumi_Stackas now explained inREADME.md.