-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InfluxDB does not support TriggerAuthentication while it is documented as such #1905
Comments
@acobaugh is working on this - Feature is done, only lacking the docs |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
ping. this fell off my radar, but still intent on finishing the docs. |
Great, thanks! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This is available in v2.4.0, would you mind giving it a go @acobaugh ? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Report
InfluxDB does not support TriggerAuthentication/ClusterTriggerAuthentication while it is documented as such
Expected Behavior
Allow you to use TriggerAuthentication/ClusterTriggerAuthentication
Actual Behavior
You can only use trigger metadata
Steps to Reproduce the Problem
Logs from KEDA operator
N/A
KEDA Version
2.3.0
Kubernetes Version
No response
Platform
No response
Scaler Details
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: