Niklas
Niklas
@mbxsuite OK, in that case you should be good process-wise. Now to address the issue at hand, do you have *BOM Processing V2* enabled in the settings? If not, give...
Where is that output from? If it is from a log of some kind, the reason why `Component`s are printed like this is just historic behavior - the `toString` method...
I'll add a mechanism to v4.12 that will "auto-repair" this.
@SaberStrat `master` has Alpine 3.1.0 now, which includes the change required for this.
Just a flaky test. I restarted CI workflow.
Oh, and consider adding a [migration](https://github.com/DependencyTrack/dependency-track/blob/master/src/main/java/org/dependencytrack/upgrade/v4120/v4120Updater.java) to remove the `badge.enabled` column from the `CONFIGPROPERTY` table. Note that #4143 also edits this file so there might be merge conflicts.
@SaberStrat Thoughts on @savek-cc's remarks? Would you be willing to refactor your work to enable backward-compatibility?
I think that might work. You can create a new team without permission, generate an API key for it, and then append `?apiKey=` to all your existing URLs. I don't...
Of course the clean way would be best. If you'd be willing to implement that, that would be awesome!
Wouldn't it be easier to just leave the existing `badge.enabled` toggle in place then? Off: Disable unauthenticated, allow authenticated+authorized On: Enable unauthenticated, allow authenticated+authorized Users who already have it enabled...