Description of APIcast parameter : APICAST_SERVICES_FILTER_BY_URL

[metaversed]

[provide a description of the issue] APIcast parameter : APICAST_SERVICES_FILTER_BY_URL

Description

Used to filter the service configured in the 3scale API Manager, the filter matches with the public base URL. Services that do not match the filter will be discarded. If the regular expression cannot be compiled no services will be loaded.

Note: If a service does not match, but is included in the APICAST_SERVICES_LIST, service will not be discarded

Steps To Reproduce

1. [step 1 (json configuration file, if applies)]
2. [step 2 (curl commands to reproduce, if applies)]
3. [step 3]

Current Result

Example:

Regexp Filter: http://.*.google.com Service 1: backend endpoint http://www.google.com Service 2: backend endpoint http://www.yahoo.com Service 3: backend endpoint http://mail.google.com Service 4: backend endpoint http://mail.yahoo.com

The services that will be configured in Apicast will be 1 and 3. Services 2 and 4 will be discarded.

Expected Result

In this case, public base URL is supposed to be a gateway URL, but example demonstrates a google URL. It is not clear if this means backend is filtered here or gateway https://github.com/3scale/apicast/blob/master/doc/parameters.md#apicast_services_filter_by_url

[eloycoto]

@raghubanda what do you want is to change the URL examples to something more API specific?

Regards.

[metaversed]

@eloycoto basically, if it can be made clear that the purpose is to fetch the configuration of the services from the Admin Portal based on a specific public base URL i.e the gateway URL . In this case google.com is more like a API backend rather than it being a gateway url instead