-
Notifications
You must be signed in to change notification settings - Fork 15
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
Why doesn't Octo STS output the error detail? #246
Comments
The policy may live in a private repo, and since we haven't authorized the caller we don't want to leak any data back to the caller. @wlynch had some work to add a validating webhook for policies, which I think may have gotten closed when I moved this into its own org, but we should potentially revisit as a way to check things before they are merged into the repository vs. at STS time. |
Thank you for your quick answer!
I see. It makes sense.
Are you talking about this pull request?
|
Yeah that’s the one. |
Revived at #247! |
Hi, thank you for your great project!
I have a question about this app.
Some error messages of this App aren't helpful.
For example, when this App can't parse trust policy, the App outputs
Error: unable to parse trust policy found for "***"
but we can't understand why.e.g.
I checked the source code then I found this App hides the error detail intentionally.
app/pkg/octosts/octosts.go
Lines 311 to 315 in 1fc549c
But I'm not sure why.
Why does this App hide an error detail?
Do we need to hide Trust Policy from clients?
Error detail would be helpful for troubleshooting.
The text was updated successfully, but these errors were encountered: