Skip to content
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

Closed
tomkerkhove opened this issue Jun 25, 2021 · 8 comments
Assignees
Labels
bug Something isn't working stale All issues that are marked as stale due to inactivity

Comments

@tomkerkhove
Copy link
Member

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

  1. Configure trigger authentication1
  2. Reference in ScaledObject with InfluxDB trigger

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

@tomkerkhove tomkerkhove added the bug Something isn't working label Jun 25, 2021
@tomkerkhove
Copy link
Member Author

@acobaugh is working on this - Feature is done, only lacking the docs

@stale
Copy link

stale bot commented Oct 13, 2021

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Oct 13, 2021
@acobaugh
Copy link
Contributor

ping. this fell off my radar, but still intent on finishing the docs.

@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Oct 13, 2021
@tomkerkhove
Copy link
Member Author

Great, thanks!

@stale
Copy link

stale bot commented Dec 13, 2021

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Dec 13, 2021
@tomkerkhove
Copy link
Member Author

This is available in v2.4.0, would you mind giving it a go @acobaugh ?

@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Dec 13, 2021
@tomkerkhove tomkerkhove moved this to Backlog in Roadmap - KEDA Core Feb 10, 2022
@stale
Copy link

stale bot commented Feb 11, 2022

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Feb 11, 2022
@stale
Copy link

stale bot commented Feb 18, 2022

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Feb 18, 2022
Repository owner moved this from To Do to Ready To Ship in Roadmap - KEDA Core Feb 18, 2022
@tomkerkhove tomkerkhove moved this from Ready To Ship to Done in Roadmap - KEDA Core Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale All issues that are marked as stale due to inactivity
Projects
Archived in project
Development

No branches or pull requests

2 participants