Update epic checklist, mark completed tasks, fix Gitea username/domain references, and update DEPLOYMENT.md with correct registry paths. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
28 lines
822 B
Markdown
28 lines
822 B
Markdown
---
|
|
# nuzlocke-tracker-jzqz
|
|
title: Configure Portainer API for automated redeployment
|
|
status: completed
|
|
type: task
|
|
priority: normal
|
|
created_at: 2026-02-09T15:30:45Z
|
|
updated_at: 2026-02-09T17:28:22Z
|
|
parent: nuzlocke-tracker-ahza
|
|
blocking:
|
|
- nuzlocke-tracker-hwyk
|
|
---
|
|
|
|
Use the Portainer CE REST API to trigger stack redeployments from the deploy script.
|
|
|
|
Portainer webhooks are a Business-only feature, so we use the API directly instead.
|
|
|
|
## Approach
|
|
|
|
1. Authenticate with the Portainer API to get a JWT token
|
|
2. Call the stack update endpoint with `pullImage: true` to pull latest images and recreate containers
|
|
|
|
## Checklist
|
|
|
|
- [ ] Identify the stack ID in Portainer (via API or UI)
|
|
- [ ] Test API authentication (`POST /api/auth`)
|
|
- [ ] Test triggering a stack redeploy via API
|
|
- [ ] Integrate into the deploy script |