## Create the Remote Terraform Repository [#create-the-remote-terraform-repository]
1. In Artifactory, go to **Administration > Repositories > Remote**
2. Click **New Remote Repository** and select **Terraform** as the package type
3. Configure the repository with these settings:
| Setting | Value |
| ---------------------- | ---------------------------- |
| Repository Key | `coder-registry` |
| URL | `https://registry.coder.com` |
| Terraform Registry URL | `https://registry.coder.com` |
4. Click **Create Remote Repository**
## Verify the Repository Configuration [#verify-the-repository-configuration]
Test that Artifactory can proxy the Coder registry by querying the module
versions API:
```sh
curl -u ':' \
'https:///artifactory/api/terraform/coder-registry/v1/modules/coder/code-server/coder/versions'
```
You should see a JSON response listing all available versions of the
`code-server` module.
## Configure Terraform CLI [#configure-terraform-cli]
Create or update your Terraform CLI configuration file to use Artifactory.
On Linux/macOS, create `~/.terraformrc`. On Windows, create `%APPDATA%\terraform.rc`.
```tf
host "" {
services = {
"modules.v1" = "https:///artifactory/api/terraform/coder-registry/v1/modules/"
}
}
credentials "" {
token = ""
}
```
Replace:
* `` with your Artifactory hostname (e.g.,
`artifactory.example.com` or `mycompany.jfrog.io`)
* `` with your Artifactory access token with read permissions to the `coder-registry` repository
The `host` block with `services` is required because Artifactory's global
service discovery endpoint doesn't include the repository name in the modules
path. This explicitly tells Terraform where to find modules in your specific
repository.
## Update Template Module Sources [#update-template-module-sources]
Update your Coder templates to use Artifactory instead of the public registry:
```tf
# Before: Direct from Coder registry
module "code-server" {
source = "registry.coder.com/coder/code-server/coder"
version = "1.4.2"
agent_id = coder_agent.main.id
}
# After: Through Artifactory mirror
module "code-server" {
source = "https:///coder/code-server/coder"
version = "1.4.2"
agent_id = coder_agent.main.id
}
```
## Configure Coder Server or Provisioners [#configure-coder-server-or-provisioners]
For Coder to use the Artifactory mirror, configure the Terraform CLI on your
Coder server or external provisioners.
Create a secret with the Terraform configuration:
```sh
kubectl create secret generic terraform-config \
--from-file=.terraformrc=./terraformrc \
-n coder
```
Update your Helm values:
```yaml
coder:
volumes:
- name: terraform-config
secret:
secretName: terraform-config
volumeMounts:
- name: terraform-config
mountPath: /home/coder/.terraformrc
subPath: .terraformrc
readOnly: true
env:
- name: TF_CLI_CONFIG_FILE
value: /home/coder/.terraformrc
```
Mount the `.terraformrc` file into the Coder container:
```yaml
# docker-compose.yaml
services:
coder:
volumes:
- ./terraformrc:/home/coder/.terraformrc:ro
environment:
TF_CLI_CONFIG_FILE: /home/coder/.terraformrc
```
## Caching Behavior [#caching-behavior]
Artifactory uses **lazy caching**, meaning modules are cached on first request.
For fully air-gapped deployments, pre-warm the cache while connected to the
internet:
1. Create a test template that references all modules you need
2. Run `terraform init` to trigger downloads
3. Verify modules appear in Artifactory under `coder-registry-cache`
Once cached, modules remain available even without internet connectivity.
## Supported Namespaces [#supported-namespaces]
The Artifactory mirror supports all namespaces from the Coder registry:
| Namespace | Description | Example Module |
| ------------ | ------------------------- | ---------------------------------- |
| `coder` | Official Coder modules | `code-server`, `jetbrains-gateway` |
| `coder-labs` | Experimental modules | `cursor-cli`, `copilot` |
| Community | Third-party contributions | Various |
All modules use the same source format:
```tf
source = "