add high-assurance placeholder option to endpoint configuration #1720
Conversation
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
LeiGlobus
added
the
no-news-is-good-news
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the skeleton of adding high-assurance to endpoint configuration.
The option in
globus-compute-endpoint configure --high-assuranceis marked as hidden for now.Like multi-user, the config is only present in the config file if it is True. The web service treats missing values as False as well.
Obviously no changelog fragment for now.
For a bit more context see SC https://github.com/globusonline/funcx-services/pull/726
This does not yet include SDK support for GET /v3/endopints/, but will shortly (or in separate PR)