-
Notifications
You must be signed in to change notification settings - Fork 167
Description
Summary
Comprehensive testing of the func subscribe command identified 5+ issues across 3 categories, with the primary concern being critical validation gaps where empty filter keys are silently accepted and written to func.yaml, creating invalid YAML that violates CloudEvents specification and will cause deployment failures; missing validation for broker names containing spaces that should be rejected according to DNS-1123 naming rules; and non-educational error messages that use technical jargon or lack helpful guidance. Key findings include the critical bug where --filter =value (empty key) succeeds silently and creates invalid YAML with an empty key string; missing validation for broker names with spaces that should be validated against DNS-1123 rules; and unclear behavior where empty paths are accepted with exit code 0 without clear indication to users. Additionally, error messages for invalid filter formats and non-existent paths are too technical (e.g., "Invalid pair:" and "stat" errors) and don't provide guidance on correct formats or what went wrong.
Full Detailed Report: Link to Google Docs - https://docs.google.com/document/d/1e-qRJu7xwc0legejWaYzIU1tV3JJK6RLuW9oN9LK2zg/edit?usp=sharing
Resolved Issues
The following issues have been marked as resolved in the detailed report:
(No issues marked as resolved yet)