feat: default interactive false in client_for_case#266
Merged
equinor-ruaj merged 1 commit intoJun 3, 2026
Conversation
5 tasks
rwiker
approved these changes
Jun 3, 2026
equinor-ruaj
deleted the
feat/default-interactive-false-in-client-for-case
branch
5 tasks
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
2 participants
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.
Issue
Closes https://github.com/equinor/sumo-core/issues/1036
Description
Related to equinor/fmu-sumo-uploader#230
When trying to authenticate using a case
sharedkeywe do not want to fall back to interactive login if it fails.How to test
Run a Drogon case without the
--sumoflag increate_case_metadataError message should be 404 instead of 401
Checklist