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

Fixed DSR difference for DS required capability #7414

Merged
merged 3 commits into from
Mar 20, 2023

Conversation

rimashah25
Copy link
Contributor

DSR difference (current value) for DS capability will only show when changes have been made to it.


Which Traffic Control components are affected by this PR?

  • Traffic Portal

What is the best way to verify this PR?

To reproduce the error,

  1. For an HTTP/DNS DS, update any value (not required capability) and submit the DSR
  2. In DSR, you will notice the diff for required capability as follows:

image

  1. Now run this branch, and check for the same error
  2. You shouldn't see the error any more.
  3. Also, ensure that when you do update required capability, DSR shows is correctly.

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

7.0.1

PR submission checklist

@ocket8888 ocket8888 added Traffic Portal v1 related to Traffic Portal version 1 regression bug a bug in existing functionality introduced by a new version labels Mar 20, 2023
@ocket8888 ocket8888 self-assigned this Mar 20, 2023
@ocket8888 ocket8888 merged commit 4194794 into apache:master Mar 20, 2023
@rimashah25 rimashah25 deleted the bugfix/dsr-ds-capability branch March 20, 2023 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression bug a bug in existing functionality introduced by a new version Traffic Portal v1 related to Traffic Portal version 1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants