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

<@U87DZN4MT>, in <https://github.com/pulumi/pulumi/issues/2788> you write


&gt;  2:   For previews and updates where we also plan to run user code, we as the language host if it knows of any plugins that may be needed. Only NodeJS &gt;implements this today, and does so by walking all the package.json's and looking for pulumi specific metadata.
&gt;
&gt;For (2), we now support the language host to communicate an optional server.


how can I change, if possible, package.json so that `pulumi plugin install` pulls plugins from a custom --server?

I think what you are asking is "what metadata can I add to my package.json file" such that when `pulumi plugin install` is run, it will use a custom server for downloading my plugin.

Unfortunately, I don't think there's a way to do that today.

A workaround would be to use the `install` section of `package.json` to have npm run `pulumi plugin install --server ...` when the package itself is installed.

Welp, I was wrong in my memory.  I think this is actually supported today :slightly_smiling_face:

Inside your `package.json` add the following:

```
pulumi: {
    resource: true,
    server: "&lt;whatever you want passed to --server&gt;"
}
```

I believe that should work.

no, still ignored :disappointed: git diff:

```
--- a/package.json
+++ b/package.json
@@ -7,4 +7,8 @@
         "@pulumi/pulumi": "latest",
         "@pulumi/gcp": "latest"
+    },
+    "pulumi": {
+      "resource": true,
+      "server": "<https://cachingproxy.mycorp/api.pulumi.com/>"
     }
 }
```

run :

```
[resource plugin gcp-0.18.13] installing
[resource plugin gcp-0.18.13] downloading from 
error: [resource plugin gcp-0.18.13] downloading from : Get <https://api.pulumi.com/releases/plugins/pulumi-resource-gcp-v0.18.13-linux-amd64.tar.gz>: dial tcp 54.213.182.12:443: connect: connection refused
```

empty `downloading from` suggests that `serverURL` is empty at that point :disappointed:

Just so I understand, <@UG53R9UJC>, you are trying to force all plugins to be be downloaded from your internal caching server (i.e. you want to force that we pull the gcp  plugin published by us at Pulumi to go through your server) or are you trying to publish a new resource provider you've created yourself?

former. Workaround I am trying now is to  parse lock file and reconstruct arguments for  `pulumi plugin install  resource gcp $ver --server`