Closed
Bug 1385857
Opened 8 years ago
Closed 8 years ago
Restrict Lando-API pingback endpoint to Transplant only.
Categories
(Conduit :: Lando, enhancement)
Conduit
Lando
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zalun, Assigned: zalun)
References
()
Details
Lando API pingback should be usable only by Transplant service.
There is a need for a specific container on which pingback will be enabled.
This endpoint will be served using a non-standard port to simplify filtering on the network layer.
Updated•8 years ago
|
Component: General → Lando API
Comment 1•8 years ago
|
||
I believe this is completed in https://github.com/mozilla-conduit/lando-api/pull/23?
If you agree and can confirm with ckolos that the infrastructure is deployed correctly then perhaps this bug is can be marked fixed.
| Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 2•8 years ago
|
||
To test if it is working one should try to hit the pingback from transplant server.
curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'API-Key: {the api key}' -d '{"landed": true, "request_id": 1}' 'https://api-private.lando.devsvcdev.mozaws.net/landings/1/update'
Status code different than 403 is valid answer.
| Assignee | ||
Comment 3•8 years ago
|
||
Could someone with access run the code above on the transplant server, please?
Flags: needinfo?(smacleod)
Flags: needinfo?(glob)
lgtm – i get 403 from the transplant server, and a timeout from home.
Flags: needinfo?(smacleod)
Flags: needinfo?(glob)
Updated•8 years ago
|
Assignee: nobody → pzalewa
You need to log in
before you can comment on or make changes to this bug.
Description
•