| Name |
Last commit
|
Last update |
|---|---|---|
| dist | ||
| hack | ||
| src | ||
| test | ||
| .editorconfig | ||
| .gitignore | ||
| .jshintrc | ||
| .npmignore | ||
| .travis.yml | ||
| Gruntfile.js | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| bower.json | ||
| package-lock.json | ||
| package.json |
The `canI` check only works if you've visited the project. This is not always true when provisioning from the catalog, so it means the secret is sometimes not displayed as a link when it should be. To provision a service or create a binding with parameters, it's required that the user create secrets anyway, so the check should never fail is permissions are set up properly. If the user doesn't have authority, the worst that happens is that they see a permission denied error following the link. In practice, it shouldn't happen. https://bugzilla.redhat.com/show_bug.cgi?id=1493439
| Name |
Last commit
|
Last update |
|---|---|---|
| dist | Loading commit data... | |
| hack | Loading commit data... | |
| src | Loading commit data... | |
| test | Loading commit data... | |
| .editorconfig | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .jshintrc | Loading commit data... | |
| .npmignore | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| Gruntfile.js | Loading commit data... | |
| LICENSE | Loading commit data... | |
| Makefile | Loading commit data... | |
| README.md | Loading commit data... | |
| bower.json | Loading commit data... | |
| package-lock.json | Loading commit data... | |
| package.json | Loading commit data... |