-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(cli): add feature to make context a required field #266
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG, thanks!
Ok(client) | ||
} | ||
|
||
const DOMAINS_THAT_REQUIRE_CONTEXT: [&str; 2] = ["uipath.com", "reinfer.io"]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would vote let's make it required for everyone until they opt out by setting the config flag honestly, I agree with you about the bad implications of uploading to the wrong place. I think quite common for even client orgs to have a staging and prod tenant right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah ok cool - did worry about that breaking any existing scripts that people have. But maybe forcing them to opt out isn't a bad thing
CHANGELOG.md
Outdated
# Unreleased | ||
- Add option to make context option a required field | ||
- Make context option a required field for internal users | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should note explicitly that this is a breaking change for reinfer/uipath users.
Makes the
re -c <context>
required if you're a UiPath user / if you opt for that in the config