Skip to content

Support consistent AI resource storage provider routing #15658

Closed

Description

@saynoword

Is your feature request related to a problem?

AI resource types currently resolve their storage provider independently. This causes several consistency problems:

  • Prompt, Skill, AgentSpec, and Agent require separate provider configuration even when they use the same storage backend.
  • Reads, draft updates, and deletes may follow the current configuration instead of the provider persisted with an existing version.
  • Prompt migration may write storage content before confirming whether the version already exists.
  • The optional AiResourceStorageBuilder contract does not clearly allow a builder to decline registration.

These behaviors make provider changes unsafe for existing resource versions and make storage plugin configuration unnecessarily repetitive.

Describe the solution you'd like

  • Add a global nacos.ai.storage.provider property for new AI resource writes.
  • Keep the existing per-resource provider properties as higher-priority compatibility overrides.
  • Persist the selected provider in each version descriptor and use that persisted provider for subsequent reads, draft updates, and deletes.
  • Treat descriptors without a provider as the legacy nacos_config provider.
  • Check whether a migrated Prompt version already exists before writing its storage content.
  • Document that an optional storage builder may return null when it should not register a provider.

The change should remain provider-neutral. Concrete external storage implementations can be supplied by separate plugins.

Additional context

The expected precedence for new writes is:

  1. Resource-specific provider property
  2. Global AI storage provider property
  3. nacos_config

Existing versions must always remain bound to the provider stored in their version descriptor.

Activity

  1. added a commit that references this issue on Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions