-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
registry-connect: what to import for API Gateway APIs? #163
Comments
This gets a high-level description of a service:
This gets the service configurations:
|
rollouts:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our first effort to import from API Gateway imports each gateway as an API and includes a deployment and spec (if the spec is available). This uses the
gateway
andapi-config
resources. These are also associated with a top-levelapi
resource, which is fairly sparse:I think it would be useful to import each of these as API resources and link them to their associated gateways, but if this is all the information we have, there's not much to put in those new API resources. I'm curious to see what's in the
managedService
records but haven't looked up how to get those from the Service Management (?) API.The text was updated successfully, but these errors were encountered: