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

Extraneous field erroneously included in Server Capability and Topology creation/modification responses #6792

Closed
ocket8888 opened this issue Apr 27, 2022 · 0 comments · Fixed by #6970
Labels
low difficulty the estimated level of effort to resolve this issue is low low impact affects only a small portion of a CDN, and cannot itself break one regression bug a bug in existing functionality introduced by a new version Traffic Ops related to Traffic Ops

Comments

@ocket8888
Copy link
Contributor

This Bug Report affects these Traffic Control components:

  • Traffic Ops

Current behavior:

Both the /topologies and /server_capabilities API endpoints will respond to POST and PUT requests with an extra, undocumented response property: RequestedName. This is likely a symptom of their use of the CRUDer (but should be easily fixable without rewriting to not use it).

The documented response examples don't include this property, and those are copy/pasted usually, so I think this is a regression bug.

Expected behavior:

That field serves no external purpose and shouldn't exist in responses ever.

Steps to reproduce:

Create a Topology or Server Capability.

@ocket8888 ocket8888 added Traffic Ops related to Traffic Ops low impact affects only a small portion of a CDN, and cannot itself break one regression bug a bug in existing functionality introduced by a new version low difficulty the estimated level of effort to resolve this issue is low labels Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low difficulty the estimated level of effort to resolve this issue is low low impact affects only a small portion of a CDN, and cannot itself break one regression bug a bug in existing functionality introduced by a new version Traffic Ops related to Traffic Ops
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant