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.

Sign up for GitHub

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

Jump to bottom

kubectl get triggerauthentication should show information about configured parameters #778

Closed
tomkerkhove opened this issue Apr 24, 2020 · 1 comment
Closed

kubectl get triggerauthentication should show information about configured parameters #778

tomkerkhove opened this issue Apr 24, 2020 · 1 comment
Assignees
@zroubalik
Labels
enhancement New feature or request feature-request All issues for new features that have not been committed to needs-discussion usability All issues related to making it easy to use KEDA
Milestone
v2.0

Comments

@tomkerkhove
Copy link
Member

As of today, kubectl get triggerauthentication shows following information:

NAME                              AGE
trigger-auth-service-bus-orders   23m

However, it would be good if it would provide information about the parameters and configured pod identity.
@tomkerkhove tomkerkhove added enhancement New feature or request needs-discussion feature-request All issues for new features that have not been committed to usability All issues related to making it easy to use KEDA labels Apr 24, 2020
@zroubalik zroubalik self-assigned this Apr 29, 2020
@zroubalik zroubalik added this to the v2.0 milestone Apr 29, 2020
@zroubalik zroubalik mentioned this issue Apr 29, 2020
Merged
@zroubalik
Copy link
Member

Fixed in $795

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zroubalik zroubalik

Labels
enhancement New feature or request feature-request All issues for new features that have not been committed to needs-discussion usability All issues related to making it easy to use KEDA
Projects
None yet
Milestone
v2.0
Development

No branches or pull requests
2 participants
@zroubalik @tomkerkhove