skills.rest
crim-ca
crim-caOFFICIAL
Explore all skills by this author →
Website𝕏@CRIM_caGitHub

provider-unregister

Remove registered providers from Weaver via DELETE requests to provider endpoints.

30|6|Updated Mar 5, 2019
Search Tags:#provider management#service integration#provider lifecycle#API request#Weaver API
One-click install
npx skills add https://github.com/crim-ca/weaver --skill provider-unregister
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: provider-unregister
Source: https://github.com/crim-ca/weaver/tree/main/.agents/skills/provider-unregister
Command: npx skills add https://github.com/crim-ca/weaver --skill provider-unregister

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of removing registered remote providers from Weaver, ensuring seamless service management and integration cleanup.

Core Features & Use Cases

  • Provider Removal: Disconnects external services from Weaver without affecting the remote service.
  • Decommissioning: Facilitates the decommissioning of service integrations and removal of outdated provider registrations.
  • Configuration Updates: Allows for updating provider configurations by unregistering and re-registering providers.
  • Lifecycle Management: Supports provider lifecycle management, from registration to decommissioning.

Quick Start

Unregister a provider using the 'provider-unregister' skill with the provider ID.

Frequently Asked Questions about provider-unregister

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I unregister a provider from Weaver?▼

Removing a provider from Weaver only disconnects the external service from the Weaver integration; it does not affect or shut down the remote service itself. This ensures seamless service management and integration cleanup without disrupting external operations.

Do I need special permissions to remove a service integration from Weaver?▼

You should unregister a provider from Weaver when decommissioning service integrations, removing outdated provider registrations, or updating provider configurations by unregistering and re-registering providers during the lifecycle management process.

What happens to the remote service when I disconnect it from Weaver?▼

Removing a provider from Weaver only disconnects the external service from the Weaver integration; it does not affect or shut down the remote service itself. This ensures seamless service management and integration cleanup without disrupting external operations.

Do I need special permissions to remove a service integration from Weaver?▼

Yes, removing a service integration from Weaver requires access to the Weaver API with specific provider management permissions. You must have these credentials and access rights to execute the DELETE request for provider decommissioning.

When should I remove a provider registration from Weaver?▼

You should unregister a provider from Weaver when decommissioning service integrations, removing outdated provider registrations, or updating provider configurations by unregistering and re-registering providers during the lifecycle management process.

Related Skills

Explore More Software Engineering Skills→
crim-cacrim-ca
30

provider-register

Register external WPS or OGC API - Processes services as remote providers in Weaver.

Official
Advanced
joshka0joshka0
3

foxctl-integrations

Synchronize AI provider and MCP integration configurations for foxctl workflows.

Community
Intermediate
NVIDIA-NeMoNVIDIA-NeMo
58

inference

Manage inference provider registration and verification within the NeMo Platform.

Official
Intermediate
crim-cacrim-ca
30

provider-list

List registered remote service providers in Weaver with URLs and availability.

Official
Basic