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

chore(admin): remove /plugins/schema/:name #10846

Merged
merged 1 commit into from
May 11, 2023

Conversation

bungle
Copy link
Member

@bungle bungle commented May 11, 2023

Summary

The /plugins/schema/:name was marked for removal in 3.0 but for some reason we forgot to do it. Doing it now.

### Summary

The /plugins/schema/:name was marked for removal in 3.0 but
for some reason we forgot to do it. Doing it now.

Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
@bungle bungle force-pushed the chore/api-remove-deprecated branch from 494fb81 to 945fb17 Compare May 11, 2023 10:33
@hanshuebner hanshuebner merged commit b3361e9 into master May 11, 2023
@hanshuebner hanshuebner deleted the chore/api-remove-deprecated branch May 11, 2023 14:30
czeslavo added a commit to Kong/go-kong that referenced this pull request May 15, 2023
The GET /plugins/schema/<pluginName> endpoint that GetSchema was using has 
been recently removed in Kong/kong#10846.
kikito added a commit that referenced this pull request Jul 27, 2023
Partially reverts #10846

Even though we have been emitting deprecation warnings when the endpoint
was used, we didn't remove it in 3.0, and doing it now can be a surprise
breaking change for someone. In fact, someone had to update a project
which was relying on that path, that is linked in #10846

This reverts the removal and replaces the deprecation version with 4.0
instead of 3.0. This PR does not revert the changes in our tests to use
the new endpoint instead of the deprecated one.
flrgh pushed a commit that referenced this pull request Jul 28, 2023
Partially reverts #10846

Even though we have been emitting deprecation warnings when the endpoint
was used, we didn't remove it in 3.0, and doing it now can be a surprise
breaking change for someone. In fact, someone had to update a project
which was relying on that path, that is linked in #10846

This reverts the removal and replaces the deprecation version with 4.0
instead of 3.0. This PR does not revert the changes in our tests to use
the new endpoint instead of the deprecated one.
team-gateway-bot pushed a commit that referenced this pull request Jul 28, 2023
Partially reverts #10846

Even though we have been emitting deprecation warnings when the endpoint
was used, we didn't remove it in 3.0, and doing it now can be a surprise
breaking change for someone. In fact, someone had to update a project
which was relying on that path, that is linked in #10846

This reverts the removal and replaces the deprecation version with 4.0
instead of 3.0. This PR does not revert the changes in our tests to use
the new endpoint instead of the deprecated one.

(cherry picked from commit 1ec4d73)
flrgh pushed a commit that referenced this pull request Jul 28, 2023
Partially reverts #10846

Even though we have been emitting deprecation warnings when the endpoint
was used, we didn't remove it in 3.0, and doing it now can be a surprise
breaking change for someone. In fact, someone had to update a project
which was relying on that path, that is linked in #10846

This reverts the removal and replaces the deprecation version with 4.0
instead of 3.0. This PR does not revert the changes in our tests to use
the new endpoint instead of the deprecated one.

(cherry picked from commit 1ec4d73)

Co-authored-by: Enrique García Cota <kikito@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants