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.

Sign up for GitHub

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

Jump to bottom

feat(config-api): managing assets(html,css,js,lib, etc) in jetty classpath will require to use Jetty API. #7932

Closed
pujavs opened this issue Mar 1, 2024 · 1 comment
Closed

feat(config-api): managing assets(html,css,js,lib, etc) in jetty classpath will require to use Jetty API. #7932

pujavs opened this issue Mar 1, 2024 · 1 comment
Assignees
@pujavs @moabu
Labels
comp-jans-config-api Component affected by issue or PR effort-5 Relative effort required for completion of issue or PR kind-enhancement Issue or PR is an enhancement to an existing functionality kind-feature Issue or PR is a new feature request priority-3 Issue or PR is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@pujavs
Copy link
Contributor

pujavs commented Mar 1, 2024 •
edited
Loading

As per custom asset management need an API to upload and manage assets in jetty classpath.
API to have upload to jetty
Parent issue: 2419

Note:

  1. Assumption to deploy assets to Jans underlying jetty server.
  2. The new endpoints will be oauth2 protected

Capturing discussion on requirement from chat:
image

Queries:

  1. On what basis will the assets be deployed in various Jetty folders?
  2. How are the assets stored in DB via DBDocumentStore are linked?
  3. Are there any special requirement apart from the Endpoint details mentioned above?
@pujavs pujavs added kind-enhancement Issue or PR is an enhancement to an existing functionality comp-jans-config-api Component affected by issue or PR effort-5 Relative effort required for completion of issue or PR priority-3 Issue or PR is relevant to core functions, but does not impede progress. Important, but not urgent labels Mar 1, 2024
@pujavs pujavs self-assigned this Mar 1, 2024
@mo-auto mo-auto added the kind-feature Issue or PR is a new feature request label Mar 1, 2024
@pujavs pujavs mentioned this issue Mar 6, 2024
Closed
@pujavs pujavs mentioned this issue Mar 20, 2024
Merged
5 tasks
@pujavs
Copy link
Contributor Author

pujavs commented Mar 20, 2024

Implemented change via PR 8096

@duttarnab duttarnab mentioned this issue Mar 21, 2024
Closed
1 task
@pujavs pujavs closed this as completed Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pujavs pujavs

@moabu moabu

Labels
comp-jans-config-api Component affected by issue or PR effort-5 Relative effort required for completion of issue or PR kind-enhancement Issue or PR is an enhancement to an existing functionality kind-feature Issue or PR is a new feature request priority-3 Issue or PR is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pujavs @moabu @mo-auto