stuartgreenshields
commented
2 years ago Current the script doesnt support wildcarding in this with the way it is written as the filtering in the APIGEE API query within the script is using the 'in' filtering expression within the APIGEE API calls, for example:-
proxy_filter="&filter=(apiproxy%20in%20${apiproxy_names})"
(apiproxy in 'ethorapi','weather-api','blah','etc')
See the bottom of this link here for information on filtering expression in APIIGEE https://cloud.google.com/apigee/docs/api-platform/analytics/analytics-reference.
However, there is a 'like' in filtering which if the script was amended there is potential to do wildcarding.
We steered away from doing this as a global common extension as there was a potential (depending on the client and as described above in the APIGEE filtering expression screenshot) for the client to collect data that was not required because of the logic in the filtering if they have 100s/1000s of API Proxies. We even found this when trying at large clients, so it meant you could pick up something that your don't want because it fits based on the wildcard filtering expression. So we went down the route of getting the client to build a list in the apiproxy.conf which is then used to build a list for the 'in' filtering expression.
We have shared Apigee with a large number of teams using it, but would like to restrict which is queried for using a wildcard.
Does the extension support this?