Skip to content
New issue

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

Feature Request : Configuring api for new MiniO architecture : #3342

Open
iamanishx opened this issue Mar 7, 2025 · 3 comments
Open

Feature Request : Configuring api for new MiniO architecture : #3342

iamanishx opened this issue Mar 7, 2025 · 3 comments
Assignees

Comments

@iamanishx
Copy link

iamanishx commented Mar 7, 2025

Is your feature request related to a problem? Please describe.
As we are implementing the new MiniO file-management system
https://docs-admin.talawa.io/docs/developer-resources/file-management

there are some changes required :

  1. configuring MiniO-endPoint for development .
  2. configuring post-table to add newly added attributes .
  3. creating a mutation to create PresignedUrl with GET object from MiniO for displaying purpose .
  4. will add if any more necessary changes needed .

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Approach to be followed (optional)
A clear and concise description of approach to be followed.

Additional context
Add any other context or screenshots about the feature request here.

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

@github-actions github-actions bot added the unapproved Unapproved for Pull Request label Mar 7, 2025
@iamanishx
Copy link
Author

@palisadoes please assign

@Cioppolo14
Copy link
Contributor

@iamanishx You have two open issues, but I think one might be ready to close? Can you clarify?

@iamanishx
Copy link
Author

@iamanishx You have two open issues, but I think one might be ready to close? Can you clarify?

No One of the issue in admin regarding minio is the parent issue of it so it's the necessity changes we need in api .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants