Skip to content

Add implementations to reserved bolt keywords #165

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Mar 25, 2019
Merged

Add implementations to reserved bolt keywords #165

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -261,6 +261,7 @@ The following keywords are keywords that must not be used by the transport schem
* `run-on` - This is used by bolt to determine which target to proxy to. Transports should not rely on this key.
* `remote-transport` - This is used to determine which transport to load. It should always be the transport class name "declassified".
* `remote-*` Any key starting with `remote-` is reserved for future use.
* `implementations`: reserved by bolt

Note: Currently bolt inventory requires that a name be set for every target and always uses that name as the URI. This means there is no way to specify `host` separately from the host section of the `name` when parsed as a URI.

Expand Down