mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node operation updates the configuration of a Redis database instance. It is useful when you need to modify settings such as memory limits or eviction policies for an existing Redis database managed through an API. Typical use cases include scaling Redis resources, tuning performance parameters, or applying new operational flags without recreating the database.

For example, you might increase the maximum memory allocation or change the eviction policy to better suit your application's caching needs.

Properties

Name Meaning
Redis Database Id The unique identifier of the Redis database instance you want to update.
Configuration A JSON object specifying the new configuration settings for the Redis database. This includes options like maxMemory, maxMemoryPolicy, and additionalFlags.

The Configuration property expects a JSON structure similar to:

{
  "additionalFlags": [null],
  "maxMemory": "64Mi",
  "maxMemoryPolicy": "allkeys-lru"
}

where you can customize memory limits and eviction policies.

Output

The node outputs JSON data representing the updated Redis database configuration as returned by the API. This typically includes confirmation of the applied settings and possibly metadata about the Redis instance after the update.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential to authenticate with the external service managing the Redis databases.
  • The node communicates with the mittwald mStudio API endpoint at https://api.mittwald.de.
  • Proper network access and permissions to update Redis database configurations via this API are necessary.

Troubleshooting

  • Invalid Redis Database Id: If the provided ID does not correspond to an existing Redis database, the API will likely return an error indicating the resource was not found. Verify the ID before running the node.
  • Malformed Configuration JSON: Ensure that the JSON provided in the Configuration property is valid and matches the expected schema. Parsing errors or invalid fields may cause the request to fail.
  • Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Confirm that the API key is correctly configured in n8n.
  • API Rate Limits or Network Issues: Temporary connectivity problems or rate limiting by the API provider can cause errors. Retrying after some time or checking network settings may help.

Links and References

Discussion