Switch PrefixCounting to RFC8040

Use RESTS_API's nonconfig endpoing and update topology selector. This
should fix first order of 404s reported in bgpcep CSIT in Chlorine and
is safe as far as back as Phosphorus.

Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Change-Id: Iebda1e88e11880b6229cc9c5e86c00ecf7257ba9

diff --git a/csit/libraries/PrefixCounting.robot b/csit/libraries/PrefixCounting.robot
index 2806ce9eccba5f0920526c92f65d8bb22638aa3a..3e0fc146b405faf2b40544b845e9385aafcd10c6 100644 (file)
--- a/csit/libraries/PrefixCounting.robot
+++ b/csit/libraries/PrefixCounting.robot
@@ -20,7 +20,7 @@ Resource          ${CURDIR}/WaitUtils.robot
 Resource          ${CURDIR}/ScalarClosures.robot
 
 *** Variables ***
-${PC_NW_TOPOLOGY}    ${OPERATIONAL_API}/network-topology:network-topology/topology
+${PC_NW_TOPOLOGY}    ${REST_API}/network-topology:network-topology/topology
 
 *** Keywords ***
 PC_Setup
@@ -32,7 +32,7 @@ Get_Ipv4_Topology
     [Documentation]    GET the ${topology} data, check status is 200, return the topology data.
     ...
     ...    Contrary to Utils.Get_Data_From_URI, this does not Log the (potentially huge) content.
-    ${response} =    RequestsLibrary.Get_Request    ${session}    ${PC_NW_TOPOLOGY}/${topology}
+    ${response} =    RequestsLibrary.Get_Request    ${session}    ${PC_NW_TOPOLOGY}=${topology}?content=nonconfig
     Run_Keyword_If    ${response.status_code} != 200    Fail    Get on ${topology} returned status code ${response.status_code} with message: ${response.text}
     [Return]    ${response.text}