Actions190
- Auth Actions
- Backup Actions
- Custom Templates Actions
- Docker Actions
- Edge Groups Actions
- Edge Jobs Actions
- Edge Stacks Actions
- Endpoint Groups Actions
- Endpoints Actions
- Endpoint Delete Batch
- Endpoint List
- Endpoint Create
- Endpoint Delete
- Endpoint Inspect
- Endpoint Update
- Endpoint Association Delete
- Endpoint Dockerhub Status
- Endpoint Edge Status Inspect
- Endpoint Force Update Service
- Endpoint Registries List
- Endpoint Registry Access
- Endpoint Settings Update
- Endpoint Snapshot
- Endpoint Update Relations
- Gitops Actions
- Helm Actions
- Intel Actions
- Kubernetes Actions
- Get All Kubernetes Applications
- Get All Kubernetes Applications Count
- Delete Cluster Role Bindings
- Delete Cluster Roles
- Get All Kubernetes Cluster Role Bindings
- Get All Kubernetes Cluster Roles
- Get All Kubernetes Config Maps
- Get All Kubernetes Config Maps Count
- Get Kubernetes Cron Jobs
- Delete Cron Jobs
- Get Kubernetes Dashboard
- Get All Kubernetes Ingress Controllers
- Update Kubernetes Ingress Controllers
- Get All Kubernetes Cluster Ingresses
- Get All Kubernetes Cluster Ingresses Count
- Delete Kubernetes Ingresses
- Get Kubernetes Jobs
- Delete Jobs
- Get Kubernetes Max Resource Limits
- Get Applications Resources
- Get Kubernetes Metrics For All Nodes
- Get Kubernetes Metrics For Node
- Get Kubernetes Metrics For All Pods
- Get Kubernetes Metrics For Pod
- Delete Kubernetes Namespace
- Get Kubernetes Namespaces
- Create Kubernetes Namespace
- Update Kubernetes Namespace Deprecated
- Get Kubernetes Namespace
- Update Kubernetes Namespace
- Get Kubernetes Config Map
- Get Kubernetes Ingress Controllers By Namespace
- Update Kubernetes Ingress Controllers By Namespace
- Get All Kubernetes Ingresses
- Create Kubernetes Ingress
- Update Kubernetes Ingress
- Get Kubernetes Ingress
- Get Kubernetes Secret
- Get Kubernetes Services By Namespace
- Create Kubernetes Service
- Update Kubernetes Service
- Kubernetes Namespaces Toggle System
- Get Kubernetes Volumes In Namespace
- Get Kubernetes Namespaces Count
- Get Kubernetes Nodes Limits
- Get Kubernetes RBAC Status
- Delete Role Bindings
- Get Kubernetes Role Bindings
- Get Kubernetes Roles
- Delete Roles
- Get Kubernetes Secrets
- Get Kubernetes Secrets Count
- Delete Service Accounts
- Get Kubernetes Service Accounts
- Get Kubernetes Services
- Get All Kubernetes Services Count
- Delete Kubernetes Services
- Get All Kubernetes Volumes
- Get Kubernetes Volume
- Get All Kubernetes Volumes Count
- Get Kubernetes Config
- Ldap Actions
- Registries Actions
- Resource Controls Actions
- Settings Actions
- Ssl Actions
- Stacks Actions
- Stack List
- Stack Delete
- Stack Inspect
- Stack Update
- Stack Associate
- Stack File Inspect
- Stack Update Git
- Stack Git Redeploy
- Stack Migrate
- Stack Start
- Stack Stop
- Stack Create Kubernetes Git
- Stack Create Kubernetes File
- Stack Create Kubernetes Url
- Stack Create Docker Standalone File
- Stack Create Docker Standalone Repository
- Stack Create Docker Standalone String
- Stack Create Docker Swarm File
- Stack Create Docker Swarm Repository
- Stack Create Docker Swarm String
- Stack Delete Kubernetes By Name
- Webhook Invoke
- Tags Actions
- Team Memberships Actions
- Teams Actions
- Templates Actions
- Upload Actions
- Users Actions
Registries → Registry Update
AI-generatedOverview
This node interacts with the Portainer API to update a specific registry entry. It is designed to modify existing registry details by sending updated information to the Portainer service. This operation is useful in scenarios where you need to programmatically maintain or synchronize container registries managed within Portainer, such as updating credentials, URLs, or other metadata related to a registry.
Practical examples include:
- Automatically updating registry credentials when they rotate.
- Changing registry URLs or names as part of infrastructure changes.
- Integrating registry updates into CI/CD pipelines for container deployments.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the registry to update. Must be provided as a number. |
| Body | The JSON string containing the updated registry details. This should include all necessary fields that define the registry configuration. |
Output
The node outputs JSON data representing the response from the Portainer API after attempting to update the registry. This typically includes the updated registry object or status information confirming the success or failure of the update operation.
No binary data output is involved.
Dependencies
- Requires an active connection to a Portainer instance via its API.
- Needs an API authentication token or key configured in the node’s credentials to authorize requests.
- The base URL for the Portainer API must be set in the credentials configuration.
Troubleshooting
- Invalid Id: If the provided registry ID does not exist, the API will likely return an error indicating the resource was not found. Verify the ID before running the node.
- Malformed Body: The body must be a valid JSON string matching the expected schema for a registry. Invalid JSON or missing required fields will cause the request to fail.
- Authentication Errors: Ensure the API key or token is valid and has sufficient permissions to update registries.
- Connection Issues: Network problems or incorrect base URL settings can prevent communication with the Portainer API.
Links and References
- Portainer API Documentation
- Portainer Registry Management (for detailed schema and examples)