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

Replacing PublishingEndpointAjaxAction by EndpointResource #28827

Closed
jdotcms opened this issue Jun 10, 2024 · 3 comments · Fixed by #31349
Closed

Replacing PublishingEndpointAjaxAction by EndpointResource #28827

jdotcms opened this issue Jun 10, 2024 · 3 comments · Fixed by #31349

Comments

@jdotcms
Copy link
Contributor

jdotcms commented Jun 10, 2024

Parent Issue

No response

User Story

As an user, I want to be able to crud endpoints on PP, so I can create the configuration for it.

Acceptance Criteria

We can replace the PP endpoint configuration by rest instead of the Ajax

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

@jdotcms jdotcms self-assigned this Jun 10, 2024
@jdotcms jdotcms moved this from New to In Progress in dotCMS - Product Planning Jun 10, 2024
@jdotcms jdotcms moved this from In Progress to In Review in dotCMS - Product Planning Jun 14, 2024
@jdotcms jdotcms moved this from In Review to In Progress in dotCMS - Product Planning Jun 14, 2024
@jdotcms jdotcms moved this from In Progress to In Review in dotCMS - Product Planning Jun 24, 2024
@dsilvam dsilvam moved this from In Review to Next 1-3 Sprints in dotCMS - Product Planning Jun 25, 2024
@jcastro-dotcms jcastro-dotcms self-assigned this Sep 3, 2024
@jcastro-dotcms jcastro-dotcms moved this from Next 1-3 Sprints to Current Sprint Backlog in dotCMS - Product Planning Sep 5, 2024
@jcastro-dotcms jcastro-dotcms moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Sep 5, 2024
@jcastro-dotcms jcastro-dotcms moved this from In Progress to Next 1-3 Sprints in dotCMS - Product Planning Sep 5, 2024
@jcastro-dotcms jcastro-dotcms removed their assignment Sep 6, 2024
@jdotcms jdotcms self-assigned this Feb 11, 2025
@jdotcms jdotcms moved this from Next 1-3 Sprints to In Progress in dotCMS - Product Planning Feb 11, 2025
Copy link

jdotcms added a commit that referenced this issue Feb 12, 2025
@jdotcms jdotcms linked a pull request Feb 12, 2025 that will close this issue
@jdotcms
Copy link
Contributor Author

jdotcms commented Feb 12, 2025

In order to test this, please refer to the PPEndpointResource postman collection

jdotcms added a commit that referenced this issue Feb 13, 2025
@jdotcms jdotcms moved this from In Progress to In Review in dotCMS - Product Planning Feb 14, 2025
github-merge-queue bot pushed a commit that referenced this issue Feb 17, 2025
Adding first draft for the pp endpoints crud on rest
@jcastro-dotcms
Copy link
Contributor

QA: PASSED ✅

  • Docker image: trunk_7716efd

The methods contained in the DWR class were migrated to new REST Endpoints correctly. Just a few things to keep in mind, that are outside the scope of this ticket:

  • The code allows you to create an PP Endpoint without its respective PP Environment. This creates orphaned Endpoints that need to be deleted directly from the database, as they won't show up in the UI.
  • The Postman test needs the code to create the JWT if it doesn't exist. If you're running the test locally, you need to manually add it.
  • The Postman test should include tests for errors as well, such as, trying to delete an Environment or Endpoint that doesn't exist.

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

Successfully merging a pull request may close this issue.

4 participants