This repository was archived by the owner on Nov 24, 2025. It is now read-only.
TP: Removes the UI screens that allow CRUD of api_capabilities#4236
Merged
ocket8888 merged 1 commit intoJan 6, 2020
Merged
Conversation
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
mitchell852
force-pushed
the
issue-4235-remove-endpoint-crud
branch
from
December 26, 2019 22:27
8349db2 to
6117605
Compare
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
Contributor
|
You've got a conflict though |
…the api_capability table. Doing this depends on endpoints that are to be deprecated.
mitchell852
force-pushed
the
issue-4235-remove-endpoint-crud
branch
from
January 6, 2020 20:49
6117605 to
f46cbad
Compare
Member
Author
resolved |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR (Pull Request) do?
Removes the ability to create, update or delete an api endpoint from the api_capability table. Doing this depends on endpoints that are to be deprecated.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
These screens were somewhat hidden in the UI as roles/capabilities has yet to implemented so you have to manually navigate to https://tp.domain.net/#!/endpoints. Ensure that the table is populated and does not include a way to edit a row or create a new row.
Also run the UI tests to ensure that TP builds and any existing functionality was not broken.
This UI functionality was never documented, therefore, there are no docs to change nor were there any UI tests to delete/change.
The following criteria are ALL met by this PR