Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

Conversation

@srijeet0406
Copy link
Contributor

@srijeet0406 srijeet0406 commented Jun 28, 2022

Closes: #6907


Which Traffic Control components are affected by this PR?

  • Traffic Ops

What is the best way to verify this PR?

Using the API, delete a server using the different API versions and make sure that the appropriate version specific server structure is returned in the response.
Make sure all the unit tests and integration tests pass.

If this is a bugfix, which Traffic Control versions contained the bug?

  • master

PR submission checklist

@srijeet0406 srijeet0406 added Traffic Ops related to Traffic Ops regression bug a bug in existing functionality introduced by a new version labels Jun 28, 2022
Copy link
Contributor

@rawlinp rawlinp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified 2.0/3.0/4.0 all return their respective server response versions

@rawlinp rawlinp merged commit f59f7d3 into apache:master Jun 28, 2022
zrhoffman pushed a commit to zrhoffman/trafficcontrol that referenced this pull request Oct 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

regression bug a bug in existing functionality introduced by a new version Traffic Ops related to Traffic Ops

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DELETE servers/{{ID}} response with an APIv4 server representation regardless of the requested version

2 participants