Import an individual template from a URL

Problem

Sharing or using a single template should not require synchronizing its entire Git Library. Users need a simple way to share a template URL and import an independent, editable copy.

Proposed workflow

1. Choose Import template from URL.
2. Paste a supported Git URL identifying a specific template directory and revision/ref.
3. Fetch and validate the complete template bundle (manifest, variable schema and files—not only template.json).
4. Review its name, description, inputs, files and resolved source revision.
5. Select a writable local Library and explicitly import the template.
6. Customize and generate using the existing template workflow.

Contract

• Import creates a local template with its own identity; it does not subscribe to updates or create an ongoing Git synchronization relationship.
• Record source URL and resolved commit for provenance without retaining credentials in that metadata.
• Fetch and import the exact snapshot reviewed by the user, even if the upstream branch changes meanwhile.
• Keep full Git Library synchronization as the separate option for maintained collections.
• Reuse existing template bundle validation/import and Git transport rather than introducing a second format or importer.
• No reusable Values, account credentials or instance settings are imported. Authored defaults/files are still untrusted content and must not be presented as secret-safe or endorsed.

Initial scope

Define and document a small, explicit set of supported Git-provider URL formats. Reject unsupported or ambiguous URLs with actionable errors; do not scrape arbitrary web pages. Downloadable bundle URLs can be considered separately rather than required for the initial Git-directory workflow.

Acceptance criteria

• A user can import one template into a local Library without adding or synchronizing the source Library.
• The complete bundle is reviewed and validated before persistence; invalid imports leave no partial template.
• The imported template is independently editable and works with existing preview, download and backend-driven CLI generation.
• Source provenance and the distinction between importing a copy and synchronizing a Library are visible and documented.
• Existing authorization, bundle/file-size limits and unsafe-path/symlink protections remain enforced.
• Remote fetching has bounded time/size and appropriate URL, redirect and network-address validation to prevent SSRF; credentials are not exposed in errors or provenance.
• Tests cover successful import, unsupported URLs, invalid bundles, unauthorized destination access and upstream revision changes between review and import.

Out of scope

Public registry hosting, publication accounts, automatic updates of imported copies, deployment/execution, and a new template package format.

This is the first feature request in the template-focused product direction: make individual templates easy to share and reuse.