-
Currently each role in backend is a hardcoded string and every time they are used, the validity of role has to be validated manually. Currently this is not much of an issue, since only few parts of th…
-
I set up the reaction manager function to read reaction role info from a file, but I think this is honestly a little bit overkill for our purposes. It makes sense for scalability (we could implement f…
-
## Bug report
### Required System information
- Node.js version: v18.17.1
- NPM version: 9.6.7
- Strapi version: 4.25.13
- Database: PostgreSQL, empty new database
- Operating system: OSX, A…
-
### Describe the Improvement
Currently it's only possible to setup an integration with S3 using Access Keys, an outdated setup which most applications have replaced with using IAM roles linked to EKS…
-
### Before reporting an issue
- [X] I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
### Are…
-
> Also, do you agree we could as a follow-up issue hard-code a list of supported roles? Could also already be done in this PR. We can give them capitalized constants, just like the permi…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Platform
all
### App version
_No response_
### Feature
The current system is pretty limited and since supp…
-
https://www.drupal.org/project/drupal/issues/468768
> For a long time I've been wondering if this was possible, and eventually I decided to try writing a patch for it :)
>
> The attached patch r…
-
### Summary
The documentation lack clarity and information about options.
For example, default and required are mutually exclusive but it is only listed in the spec of the module https://docs.an…
-
## Describe the bug
ocis has still quite a few place where it using hardcoded UUIDs:
* as already mentioned the admin user (#3524) and the settings service user (#3343) use hardcoded UUIDs
* al…