Skip to content
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

Update component code coverage and dependencies docs #531

Merged
merged 1 commit into from
Apr 29, 2019
Merged

Update component code coverage and dependencies docs #531

merged 1 commit into from
Apr 29, 2019

Conversation

ukclivecox
Copy link
Contributor

No description provided.

@ukclivecox ukclivecox merged commit 250bf16 into SeldonIO:master Apr 29, 2019
@ukclivecox ukclivecox deleted the components_mvn_docs branch February 14, 2020 11:39
agrski added a commit that referenced this pull request Dec 2, 2022
* Rename method for semantic clarity

This method returns a completely new, fresh connection every time,
whereas 'get' implies potential reuse of an existing object.

* Add authority param to scheduler client constructor + update callers

* Reorganise gRPC connection method into per-dial option sections

* Create list of dial opts atomically instead of appending in gRPC connection setup

This makes it easier to see which dial options are being set, especially with more complex logic or if we add chained interceptors.

* Split flag/env var/default constants into separate blocks for clarity

* Fix typo in name of default var

* Add authority option to gRPC connection creation in scheduler client

* Make CLI cmd package-only constants private instead of public

* Rename CLI flag vars to use 'flag' as the prefix

This aids discoverability, implies logical grouping of all flag variables (this is harder to determine with suffixes),
and is consistent with the env vars and defaults.

* Order blocks of CLI flags/env vars/defaults alphabetically

* Use constant for scheduler-host help statement in CLI commands

Rather than replicating the same string in about 15 different places and risking typos or inconsistencies,
we can use a single constant.

* Add constants for shared flag help docs for CLI subcommands

* Reword some command flag help docs for clarity

* Add authority flag to CLI subcommands communicating with the scheduler

* Reorder statements & add blank lines for logical grouping

* Add authority flag for model metadata subcommand & use in REST call to server

* Reorder lines for legibility

* Update help message for header flag

* Order help messages alphabetically

* Fix typo in var name

* Rename flag var for consistency

* Move sticky session flag to flags file as shared between subcommands

* Rename more flag vars for consistency of format, i.e. flagX not xFlag
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants