Portainer icon

Portainer

Interact with Portainer via API

Actions190

Custom Templates → Custom Template Create File

AI-generated

Overview

This node operation allows users to create a custom template file in the "Custom Templates" resource. It is designed to facilitate the creation and management of template files associated with different platforms and stack types, such as Linux or Windows platforms and stack types like swarm, compose, or Kubernetes. This can be particularly useful for automating deployment configurations, infrastructure as code templates, or reusable environment setups.

Practical examples include:

  • Creating a Docker Compose template file for a Linux platform.
  • Uploading a Kubernetes deployment template with descriptive metadata.
  • Managing reusable stack templates with notes and logos for easy identification in a UI.

Properties

Name Meaning
Title Title of the template.
Description Description of the template.
Note A note displayed in the UI; supports HTML content.
Platform Platform associated with the template. Options: 1 (linux), 2 (windows).
Type Type of created stack. Options: 1 (swarm), 2 (compose), 3 (kubernetes).
File The actual file content or reference representing the template file.
Logo URL of the template's logo image.
Variables JSON array defining variables used within the template.

Output

The node outputs JSON data representing the result of the template creation operation. This typically includes confirmation details about the newly created template, such as its ID, metadata, and any server response confirming success.

If the node handles binary data (e.g., the template file itself), it would be included in the output, but based on the provided properties, the file is sent as part of the request body rather than outputted as binary.

Dependencies

  • Requires an API key credential for authenticating with the Portainer API.
  • Needs the base URL of the Portainer instance configured in credentials.
  • Depends on the Portainer API being accessible and supporting the custom template creation endpoint.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API keys.
    • Incorrect platform or type values leading to API validation errors.
    • Malformed JSON in the Variables property causing request rejection.
    • Missing required fields like Title, Description, Note, Platform, Type, or File.
  • Error messages:

    • Unauthorized or 401 errors: Check API key validity and permissions.
    • Validation errors from the API: Verify that all required fields are correctly filled and that enumerated options match expected values.
    • JSON parsing errors: Ensure the Variables field contains valid JSON.

Links and References


Note: The above summary is based solely on static analysis of the provided source code and property definitions without runtime execution.

Discussion