-
Notifications
You must be signed in to change notification settings - Fork 1.4k
🌱 Add enable_core_provider option support in tilt-settings.yaml|json file #11879
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
🌱 Add enable_core_provider option support in tilt-settings.yaml|json file #11879
Conversation
docs/book/src/developer/core/tilt.md
Outdated
**disable_providers** (Array[]String, default=[]): A list of the providers to disable. By default, the `core` provider is always installed. You can also disable it. | ||
|
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.
Let's instead just add a bool disable_core_provider
. All others are already opt-in.
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.
Yes, sure, it was my original approach, but tried to do more flexible.
Ok, let's revert it.
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 also wasn't sure, but I think Christian's suggestion is fine. I don't foresee us adding any other default providers
Is it also possible to have enable_core_provider and default it to true?
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.
Fixed.
Added disable_core_provider option which is False by default.
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 just flip it around and call it enable_core_provider and default True. We already have enable_providers + double negation is never great
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.
Ok, switched to enable_core_provider
option which allows to disable it.
748b5ef
to
a015615
Compare
a015615
to
03a7288
Compare
03a7288
to
5ce8edb
Compare
Thx! /lgtm Would be good if someone can do quick manual tests with/without the setting before we merge this PR |
LGTM label has been added. Git tree hash: 47834b1f5a133661ef087d016a84868a57b091c3
|
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.
Tested all three:
enable_core_provider: true
enable_core_provider: false
# enable_core_provider: false
/approve
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: chrischdi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This allows to disable
core
(or any others in the future) provider enabled by defaultWhich issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #11854
/area devtools