Pulumi Automation API cannot correctly import components.

What happened?

We have a custom component we wrote to homogenize how we declare our IAC. It essentially just has some thin wrappers around the AWS plugin.

Our devops team wrote this component (package) in pulumi-ts and run gen-sdk --local --language java to generate a maven jar we assume is usable from any one of our projects.

Once deployed as a jar in our m2 repository and brought in as a dependency for building our java based automation api application we get the following error:

[71] error: Could not automatically download and install resource plugin 'pulumi-resource-atn-iac-components' at version v0.0.0, install the plugin using `pulumi plugin install resource atn-iac-components v0.0.0`: error downloading provider atn-iac-components to file: failed to download plugin: atn-iac-components-0.0.0: 403 HTTP error fetching plugin from

Like I started mentioning before, this isn't a public plugin and there's very little in the automations API on how to procede from here; I asked in the slack channel about this and was redirected towards creating this issue.

Tnanks.

Example

simply generate and publish any component and try to import it via the java automations api.

Output of pulumi about

N/A this is an automations application

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Start with the Java Automation API path that imports components generated by gen-sdk --local --language java, using the published Maven jar and the reported private-plugin download failure as the reproduction. Done means a generated private component can be imported through the Java Automation API without attempting an unavailable public plugin download.