To-do List Gateway
To provide public access to your new deployment, you need to configure one of the existing API gateways or deploy a new one.
Last updated
Core Platform
To provide public access to your new deployment, you need to configure one of the existing API gateways or deploy a new one.
Last updated
Open the Gateway > Channel screen from your Devops app. Unless you've modified your implementation, this screen is located at https://[YOUR_ADMIN_UI_DOMAIN]/app/devops/common/gateway_channel.
Next, you will create a new API channel on this new Gateway System to assign a specific URL path to your deployment.
Click on "CREATE NEW" button, assign "todo_crud" as the id, enter the following details and save:
DEFINITION
Channel Name: Todo
Channel Status: ACTIVE
Description: CRUD path to todo list runner
Applicable Gateways: admin-prod
System Executor: CRUD
System Parameters:
Key: server.baseUrl, Value: http://runner-example-0001-service.admin-backend.svc.cluster.local:1235
Target: /api/todo
AUTHENTICATION
Path Authentications: { "*": { "isPublic": true } }
These settings will map "todo_crud" endpoint on "admin-prod" gateway to "/api/todo" endpoint of your "example-0001" deployment. The authentication settings provide public access to all paths on this endpoint.
After saving the new channel, your settings will be automatically applied to your gateway (after a few seconds as defined in configuration). You can also refresh gateway settings manually, by making calls to the following endpoints using your favorite API client:
Now, you can access your todo list APIs publicly through your gateway. Test your access by listing the record you've created in last section by:
Please note that you only need to create new gateway mappings when you create microservices that should be directly accessible by end users.
