-
Notifications
You must be signed in to change notification settings - Fork 361
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Client can specify **destination ports**
This also enables support for Docker apps not listening on port 8080 This affects two 2 endpoints: - POST `/v3/routes/route_GUID/destinations` - PATCH `/v3/routes/route_GUID/destinations` |**field**| **required**|**default** | **validations**| |---|---|---| |port|no| 8080 | integer, min 1024, max 65535 | **Example Object** ```json { "guid": "c87ebef2-fd8d-462d-9825-228f3055ddf2", "app": { "guid": "first-app-guid", "process": { "type": "web" } }, “weight”: 30, "port": 1234 } ``` When _no_ port is specified on the destination, we adhere to the following behavior: | User Set Port | App Lifecycle | Staged | Display | |---------------|---------------|----------|---------------------| | true | anything | anything | user-specified port | | false | buildpack | anything | 8080 | | false | docker | false | 8080 | | false | docker | true | execution metadata 1st port OR 8080 | Per Greg Cobb: > In short: the displayed port should be the same as the port that will be used When a destination is created to a certain port on a process, we notify Diego that this process should have that port open; in V2 we didn't. [finishes #166091491] [fixes #167149569] Co-authored-by: Reid Mitchell <[email protected]> Co-authored-by: Eli Wrenn <[email protected]> Co-authored-by: Supraja Narasimhan <[email protected]> Co-authored-by: Piyali Banerjee <[email protected]> Co-authored-by: Brian Cunnie <[email protected]> Co-authored-by: Luan Santos <[email protected]>
- Loading branch information
1 parent
4b529af
commit e1a87d7
Showing
16 changed files
with
945 additions
and
311 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.