We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently it's not possible to generate a sealed secret via the /api/raw endpoint for different scopes than the default one (strict).
/api/raw
The error seems to be in the 'Raw' function. Instead of using the predefined scope
sealed-secrets-web/pkg/seal/seal.go
Lines 92 to 95 in d8d9dce
the 'kubeseal.EncryptSecretItem' is called with 'v1alpha1.DefaultScope' again
Line 98 in d8d9dce
Please ignore this analysis if I'm wrong. I'm not a Go developer. Might be also that I'm used the API in a wrong way. This is how I used it:
curl --request POST 'https://<my-cluster-url>/api/raw' \ ─╯ --header 'Content-Type: application/json' \ --data '{ "scope": "cluster-wide", "value": "value to seal" }'
PS: Anyway. Great tool. Thanks for sharing it.
The text was updated successfully, but these errors were encountered:
#181 pass provided scope
bd9a04f
Hi @mkschuel
You're right, this seems not to work as expected. Thank you very much for reporting.
I'll provide a new version ASAP
Sorry, something went wrong.
No branches or pull requests
Currently it's not possible to generate a sealed secret via the
/api/raw
endpoint for different scopes than the default one (strict).The error seems to be in the 'Raw' function. Instead of using the predefined scope
sealed-secrets-web/pkg/seal/seal.go
Lines 92 to 95 in d8d9dce
the 'kubeseal.EncryptSecretItem' is called with 'v1alpha1.DefaultScope' again
sealed-secrets-web/pkg/seal/seal.go
Line 98 in d8d9dce
Please ignore this analysis if I'm wrong. I'm not a Go developer.
Might be also that I'm used the API in a wrong way. This is how I used it:
PS: Anyway. Great tool. Thanks for sharing it.
The text was updated successfully, but these errors were encountered: