Deliveryservice Topologies#4692
Conversation
…d with a ds, not just the ones explicitly assigned to a ds. i.e. the mids too to paint a better picture of which servers are employed either explicitly (edges and orgs) or implicitly (mids).
adb1f6c to
bacb7a1
Compare
zrhoffman
left a comment
There was a problem hiding this comment.
TO API tests pass, TO unit tests pass, gofmt does not change the formatting of files changed in this PR, and the docs build without warnings related to this PR and look good.
The Traffic Portal portion of this PR also needs to be reviewed.
ocket8888
left a comment
There was a problem hiding this comment.
I left all of my DS form comments on the DNS template - but they (probably mostly) apply to all of them
| <li role="menuitem"><a ng-click="viewCharts()">View Charts</a></li> | ||
| <hr class="divider"/> | ||
| <li role="menuitem"><a ng-click="viewServers()">Manage Servers</a></li> | ||
| <li ng-if="::(!deliveryService.topology)" role="menuitem"><a ng-click="viewServers()">Manage Servers</a></li> |
There was a problem hiding this comment.
IMO these should be !(deliveryservice.Topology instanceof Object)
There was a problem hiding this comment.
Nah
const a = {topology: "test"};
console.log(a.topology instanceof Object); // falseThere was a problem hiding this comment.
Oh, that's just the name. typeof deliveryService.Topology !== 'string' in that case
There was a problem hiding this comment.
But then you could have
const a = {topology: ""};
console.log(typeof a.topology === "string"); //trueThere was a problem hiding this comment.
True, the loose comparison is useful in this case.
What does this PR (Pull Request) do?
Add a new
Topologyfield to Delivery Services in TO API 3.0 in order to assign Delivery Services to Topologies.topologyfield #4569Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
The following criteria are ALL met by this PR