The goal is to move away from static, manual-entry text fields—which are prone to "fat-fingering" and input errors—and move toward a real-time, validated lookup component.

Core Functionality

Asynchronous Lookup: The UI component should perform an asynchronous GET request to a customer-defined REST API endpoint as the user types.

Search Debouncing: To prevent overwhelming the external API, the request should only trigger after a specific character threshold (e.g., 3 characters) or a short delay (300ms) in typing.

Key-Value Separation: * Display Value: What the user sees (e.g., "Payment-Processing-Service").

Stored Value: The actual unique identifier (e.g., "V-99827") that is passed into the underlying YAML and used for provisioning.

Validation Enforcement: The workflow should prevent submission if the user tries to enter a value that was not returned by the API search, ensuring that only "existing and valid" entities are used.