You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a document that outlines use cases for the HTTP add on.
Use-Case
The document should be used by users (prospective and current) of the HTTP add on to guide their decision to use the project, and by developers to decide if/how a feature will fit.
Specification
A new document with use cases on it
A link from the README to this new document
The text was updated successfully, but these errors were encountered:
* Adding a use cases document.
Fixes#81
Signed-off-by: Aaron Schlesinger <aaron@ecomaz.net>
* alphabetically sorting list of providers
Signed-off-by: Aaron Schlesinger <aaron@ecomaz.net>
* adding steps to move to KEDA-HTTP for use case 1
Signed-off-by: Aaron Schlesinger <aaron@ecomaz.net>
* steps for migrating for use case 2
Signed-off-by: Aaron Schlesinger <aaron@ecomaz.net>
* adding color coding
Signed-off-by: Aaron Schlesinger <aaron@ecomaz.net>
* Update docs/use_cases.md
Signed-off-by: Aaron Schlesinger <aaron@ecomaz.net>
Co-authored-by: Tom Kerkhove <kerkhove.tom@gmail.com>
Signed-off-by: Aaron Schlesinger <aaron@ecomaz.net>
Co-authored-by: Tom Kerkhove <kerkhove.tom@gmail.com>
kingdonb
pushed a commit
to kingdonb/http-add-on
that referenced
this issue
Jun 12, 2023
We need a document that outlines use cases for the HTTP add on.
Use-Case
The document should be used by users (prospective and current) of the HTTP add on to guide their decision to use the project, and by developers to decide if/how a feature will fit.
Specification
The text was updated successfully, but these errors were encountered: