Microsoft Azure RedisManagementClient

What authentication does the Azure Redis Management API use?

The API runs through Azure Resource Manager and uses OAuth 2.0 bearer tokens issued by Azure Active Directory under the azure_auth scheme with the user_impersonation scope. Through Jentic, the AAD client secret is held in the encrypted vault and a short-lived access token is supplied at execute time so the secret never appears in the agent's context.

Can I rotate Redis access keys without downtime?

Yes. Use POST .../Redis/{name}/regenerateKey to regenerate one of the two keys while applications continue to use the other. Once the application has switched, regenerate the second key as well. The listKeys POST endpoint returns the current pair.

What are the rate limits for the Azure Redis Management API?

Azure Resource Manager applies subscription-level read and write throttles (around 12,000 reads per hour and 1,200 writes per hour per region per subscription) and returns 429 with a Retry-After header when exceeded. Cache create, update, import, and export are long-running operations and should be polled with backoff.

How do I provision an Azure Redis cache through Jentic?

Search Jentic for 'provision azure redis cache', load the schema for PUT .../Microsoft.Cache/Redis/{name}, then execute with subscriptionId, resourceGroupName, name, location, and an sku block. The pip install jentic Python SDK uses the async search, load, execute pattern.

Is the Azure Redis Management API free?

There is no per-call charge for the management API itself; you pay for the Redis cache SKU and capacity by the hour. Premium SKUs are billed higher than Basic and Standard but are required for features like linked-server geo-replication, persistence, and clustering.

Can I limit what my agent is allowed to do with the Redis Management Client API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the subscription, resource group, and cache name all travel in the URL path, so a rule can pin the agent to a single cache. You pick the operations it may call, for example reading a cache and configuring its firewall rules, while leaving out destructive ones like regenerating an access key or forcing a reboot unless you explicitly add them. The Azure AD credential is stored once by your own instance, and only a scoped bearer token is supplied at execution time so the client secret and returned Redis access keys never reach the agent's context.