mrsaints / kubeseal-web Goto Github PK

We can remove the need for pkger.

https://golang.org/pkg/embed/

It can get a little confusing when sealing multiple secrets because there is no clear indicator if the updated raw secret was successfully sealed, and if we even triggered the sealing.

Some ideas:

• Reset the sealed secret output if the raw secret changes
• Disable the seal button after sealing, and only re-enable it if the raw secret changes
• Include an indicator (e.g. icon or message) that the raw secret is "dirty" and needs sealing
• Show a sealed success message or a loading state (maybe something similar to React Suspense, only show it if it takes longer than normal)

https://github.com/bitnami-labs/sealed-secrets#scopes

Otherwise, it is not very clear if a secret was sealed successfully.

1. Seal an invalid secret
2. Seal a valid secret
3. The error message from (1) does not disappear