-
Notifications
You must be signed in to change notification settings - Fork 145
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
VMAuth skip broken VMUsers during config building #1047
Labels
bug
Something isn't working
Comments
f41gh7
added a commit
that referenced
this issue
Jul 29, 2024
Changes behaviour of VMAuth config generation: * now it skips misconfigured VMUser objects and continues config generation without it * misconfigured VMUsers marked with error at lastSyncError field * configuration checks better for misconfiguration (properly deduplicate user tokens, checks static url links and result url_map) Performs refactoring for CRDRef fetching. Use generic interface and reduce copy-paste. Introduce new status field for VMUser - `lastSyncError`. Adds column print for it. #1047 Signed-off-by: f41gh7 <[email protected]>
f41gh7
added a commit
that referenced
this issue
Jul 30, 2024
f41gh7
added a commit
that referenced
this issue
Jul 30, 2024
Changes behaviour of VMAuth config generation: * now it skips misconfigured VMUser objects and continues config generation without it * misconfigured VMUsers marked with error at lastSyncError field * configuration checks better for misconfiguration (properly deduplicate user tokens, checks static url links and result url_map) Performs refactoring for CRDRef fetching. Use generic interface and reduce copy-paste. Introduce new status field for VMUser - `lastSyncError`. Adds column print for it. #1047 Signed-off-by: f41gh7 <[email protected]>
AndrewChubatiuk
added
the
waiting for release
The change was merged to upstream, but wasn't released yet.
label
Aug 12, 2024
released in v0.47.0 |
AndrewChubatiuk
removed
the
waiting for release
The change was merged to upstream, but wasn't released yet.
label
Aug 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, a single VMUser with incorrect configuration could break VMAuth config generation.
It must be changed in the same way, as currently handled scrape objects.
It needed because VMUser object could be created by non-owner of VMAuth.
It'd be great in addition:
The text was updated successfully, but these errors were encountered: