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

vendor your modules <https://go.dev/ref/mod#go-mod-vendor>

I don't want to vendor them, just cached them

also even if I vendor the go modules, Pulumi is still going to download the Pulumi modules:

[resource plugin cloudflare-3.6.0] installing
`[resource plugin aws-4.38.1] installing`
`[resource plugin aws-5.38.0] installing`

<@U052GTFG4PR> is this on Github Actions?

You can use `PULUMI_HOME` to configure where these plugin binaries are downloaded on your CI runners. (<https://www.pulumi.com/docs/reference/cli/environment-variables/>)
If you combine this with the caching behaviour your CI system might offer, you can improve the speed of subsequent runs. For Gitlab, I think this is the page to look at in their docs:
<https://docs.gitlab.com/ee/ci/caching/>

```deploy:
  interruptible: true
  needs:
    - build
  stage: deploy
  image: pulumi/pulumi-go
  before_script:
    - mkdir -p ${CI_PROJECT_DIR}/.cache
    - export GOPATH=${CI_PROJECT_DIR}/.cache
    - apt update &amp;&amp; apt install -y make &amp;&amp; apt clean
  cache:
    policy: pull-push
    when: on_success
    key: build
    paths:
      - .cache
      - /root/.pulumi/plugins
  script:
    - make deploy```

```    - mkdir -p ${CI_PROJECT_DIR}/.pulumi
    - export PULUMI_HOME=${CI_PROJECT_DIR}/.pulumi```
then I'll cache it
```  cache:
    policy: pull-push
    when: on_success
    key: build
    paths:
      - .cache
      - .pulumi/plugins```

```Saving cache for successful job
Creating cache build-protected...
.cache: found 14914 matching artifact files and directories 
.pulumi/plugins: found 19 matching artifact files and directories ```
works guys!