deep-stack/stack-orchestrator
3
0
Fork 0
forked from cerc-io/stack-orchestrator
Code Pull Requests Activity

Rename image-registry to registry-credentials to avoid collision

Browse Source 
The existing 'image-registry' key is used for pushing images to a remote
registry (URL string). Rename the new auth config to 'registry-credentials'
to avoid collision.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
A. F. Dudley 2026-02-03 12:30:35 -05:00
parent 73ba13aaa5
commit cb6fdb77a6
2 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/deployment_patterns.md
View File

@ -82,10 +82,10 @@ For deployments using images from private container registries (e.g., GitHub Con
### Configuration
Add an `image-registry` section to your spec.yml:
Add a `registry-credentials` section to your spec.yml:
```yaml
image-registry:
registry-credentials:
server: ghcr.io
username: your-org-or-username
token-env: REGISTRY_TOKEN
@ -121,6 +121,6 @@ When using Ansible for deployments, pass the token from a credentials file:
### How It Works
1. laconic-so reads the `image-registry` config from spec.yml
1. laconic-so reads the `registry-credentials` config from spec.yml
2. Creates a Kubernetes `docker-registry` secret named `{deployment}-registry`
3. The deployment's pods reference this secret for image pulls

5
stack_orchestrator/deploy/spec.py
View File

@ -103,8 +103,11 @@ class Spec:
Used for private container registries like GHCR. The token-env field
specifies an environment variable containing the API token/PAT.
Note: Uses 'registry-credentials' key to avoid collision with
'image-registry' key which is for pushing images.
"""
return self.obj.get("image-registry")
return self.obj.get("registry-credentials")
def get_volumes(self):
return self.obj.get(constants.volumes_key, {})