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

Determine which QS access licenses to release in a more effective way than today #1103

Closed
mountaindude opened this issue Apr 22, 2024 · 1 comment
Labels
delivered This feature has been included in Butler enhancement

Comments

@mountaindude
Copy link
Collaborator

What version of Butler are you using?

12.1.1

What version of Node.js are you using? Not applicable if you use the standalone version of Butler.

What command did you use to start Butler?

What operating system are you using?

What CPU architecture are you using?

What Qlik Sense versions are you using?

2024-Feb

Describe the Bug

In current Butler version a list of all assigned licences (professional and analyzer, respectively) is extracted, then the lastUsed property is examined for all those users.

On large QS environments (thousands of users and more) this may result in the licenses release process taking a long time.
Especially considering that the most likely scenario is that only a few users' licenses will be released.

A better solution is to apply a filter when retrieving the list of which users have (for example) professional licenses, with the effect that we instead get a list where all licences should be released.

The filter is a URL parameter: filter=lastUsed le '2024-04-22T23:59:59' will get all users with who used their licences before that timestamp.

Expected Behavior

No response

To Reproduce

No response

mountaindude pushed a commit to mountaindude/butler that referenced this issue Apr 23, 2024
@mountaindude mountaindude added enhancement delivered This feature has been included in Butler labels Apr 25, 2024
@mountaindude
Copy link
Collaborator Author

Released in 12.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
delivered This feature has been included in Butler enhancement
Projects
None yet
Development

No branches or pull requests

1 participant