build/oauth2: properly check clientID for empty value #1563
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Previously, oauth2 configuration with empty clientID produced weird key not found error. It could break vmagent entier config generation. This commit adds explicit check for clientID to be non-empty and an additional assert into builder function.
Updated the CHANGELOG to include a link to PR #1563 for the oauth2 configuration bugfix.
AndrewChubatiuk approved these changes Oct 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Previously, oauth2 configuration with empty clientID produced weird key
not found error. It could break vmagent entier config generation.
This commit adds explicit check for clientID to be non-empty and an
additional assert into builder function.