add "create configuration" support for SH hosting in orders and subs#1095
Merged
add "create configuration" support for SH hosting in orders and subs#1095
Conversation
pl-gideon
approved these changes
Jan 28, 2025
This file contains hidden or 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
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.
Related Issue(s):
Closes #
Proposed Changes:
For inclusion in changelog (if applicable):
create_configurationfor Sentinel Hub hosting supported in Orders and Subscriptions Python SDK--create-configurationfor Sentinel Hub hosting supported in Orders and Subscriptions CLINot intended for changelog:
Diff of User Interface
Old behavior:
New behavior:
create_configurationin:build_requestbuild_requestplanet orders requestplanet orders createplanet subscriptions requestplanet subscriptions createNote: create configuration and collection id are mutually exclusive but I have chosen to clean on the API to validate and not do that client side. So a
requestcan be built successfully that will fail when submitted to the API.PR Checklist:
(Optional) @mentions for Notifications:
@pl-gideon