Unable to create secrets in latest release candidate

[radeusgd]

Enso_99ze5IbcPx.mp4

I was testing rc5 and trying to create a secret. Clicking on Create seems to do nothing and the secret is not created. The console prints the following errors:

POST https://7aqkn3tnbc.execute-api.eu-west-1.amazonaws.com/secrets 403 (Forbidden)
Could not create secret with name 'test-secret-23': unknown error.

[radeusgd]

Okay I was told that this view tries to create the secret in the root directory and that's why it fails.

So the problem is there is no error message displayed.

Similarly, when I entered home and tried creating a duplicated secret there, I also get no error message in the GUI - only in the logs I can see what went wrong:

index-BJZce-Cm.js:22 Could not create secret with name 'gh1': A resource with that name already exists. Use a different, unique value for `name` and try again..

We need to expose the error messages to the users.

[jdunkerley]

selecting the folder doesn't change the creation target - we need to do some design work on the asset view but that wont be for the release.

[radeusgd]

selecting the folder doesn't change the creation target - we need to do some design work on the asset view but that wont be for the release.

Fair, but can we at least expose the errors to the users as some notification bubble / alert? Currently the errors are only visible in the console logs that is not supposed to be opened by users (it has the big 'warning' written on it) which is very confusing because it just looks like the Create button does not do anything at all.