-
Notifications
You must be signed in to change notification settings - Fork 217
Description
Release version
v5.1.1
Question Details
Our APIM solely uses self-hosted gateways and thus does not require every API to be assigned to the "Managed" gateway.
However, even though the API is only assigned to a specific self-hosted gateway, the "Managed" gateway is still getting assigned to it.
I added a "Managed" gateway into the gateways
directory and set the APIs to an empty array.
However, this only works when not using the commit id during publishing, as the Managed gateway file is not changed when I add a new API.
How is this supposed to be handled?
Expected behavior
"Managed" gateway is not assigned whenever I assign it to some custom gateways.
Actual behavior
"Managed" gateway is always assigned to new APIs.
Reproduction Steps
Create a fresh API and assign it to a custom gateway (not the "Managed" one)
Content of gateways/self-hosted/apis.json
[
{
"name": "my-new-api"
}
]
Content of gateways/Managed/apis.json
[]
Since the gateways/Managed/apis.json
has not been touched/changed during the commit, the publisher does not update the Managed gateway assignment, so the new API is actually having both the "Managed" and "self-hosted" gateways assigned to it.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status