michael-s-molina commented on code in PR #36298: URL: https://github.com/apache/superset/pull/36298#discussion_r2566442389
########## docs/developer_portal/extensions/deployment.md: ########## @@ -33,13 +33,17 @@ Packaging is handled by the `superset-extensions bundle` command, which: 3. Generates a `manifest.json` with build-time metadata, including the contents of `extension.json` and references to built assets. 4. Packages everything into a `.supx` file (a zip archive with a specific structure required by Superset). -Uploading is accomplished through Superset's REST API at `/api/v1/extensions/import/`. The endpoint accepts the `.supx` file as form data and processes it by: +To deploy an extension, place the `.supx` file in the extensions directory configured via `EXTENSIONS_PATH` in your `superset_config.py`: -1. Extracting and validating the extension metadata and manifest. -2. Storing extension assets in the metadata database for dynamic loading. -3. Registering the extension in the metadata database, including its name, version, author, and capabilities. -4. Automatically activating the extension, making it immediately available for use and management via the Superset UI or API. +``` python +EXTENSIONS_PATH = "/path/to/extensions" +``` -This API-driven approach enables automated deployment workflows and simplifies extension management for administrators. Extensions can be uploaded through the Swagger UI, programmatically via scripts, or through the management interface: +During application startup, Superset automatically discovers and loads all `.supx` files from this directory: Review Comment: The development mode combined with Superset's auto-reloading offers this type of functionality. In production, this is probably controlled by your deployment orchestrator like Spinnaker. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
