fix PluginDaemonInternalServerError: no available node, plugin runtime not found (#549)

* fix PluginDaemonInternalServerError: no available node, plugin runtime not found

Fix the bug where after a plugin is successfully upgraded, new requests result in the plugin daemon service responding with "no available node, plugin runtime not found".

The root cause is that when the plugin is upgraded successfully, the corresponding value in Redis is not updated. Consequently, when a new request arrives, it reads the outdated plugin version from Redis and fails to locate the correct runtime.

* raise error if failed

Author: SongYippee

internal/types/models/curd/atomic.go

@@ -2,6 +2,8 @@ package curd
 
 import (
 	"errors"
+	"github.com/langgenius/dify-plugin-daemon/pkg/utils/cache"
+	"github.com/langgenius/dify-plugin-daemon/pkg/utils/cache/helper"
 
 	"github.com/langgenius/dify-plugin-daemon/internal/db"
 	"github.com/langgenius/dify-plugin-daemon/internal/types/models"
@@ -602,6 +604,10 @@ func UpgradePlugin(
 	if err != nil {
 		return nil, err
 	}
-
+    pluginId := newPluginUniqueIdentifier.PluginID()  // get the pluginId
+	pluginInstallationCacheKey := helper.PluginInstallationCacheKey(pluginId, tenantId) // make cache key
+	if _, err = cache.AutoDelete[models.PluginInstallation](pluginInstallationCacheKey); err != nil {
+		return nil, err
+	}
 	return &response, nil
 }