Closed andreaTP closed 1 year ago
Thanks @MikeEdgar for the prompt answer, no we got it on the list topics endpoint, I can remove the 403 from /acls/resource-operations
if desired.
I can remove the 403 from
/acls/resource-operations
if desired.
I think it's fine to declare it on all of them :+1:
the CI got stuck apparently, something to do with this PR?
the CI got stuck apparently, something to do with this PR?
I don't think it's due to these changes. Probably just GitHub load or service issues. I just retriggered it.
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
We have noticed that more endpoints were throwing 403 responses. Since the mapper for 403 is common I expanded the specification to keep 403 always into account.
This change is needed to generate better/nicer error-handling code in generated clients.