-
Notifications
You must be signed in to change notification settings - Fork 244
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
Rename generic run-on flag into platform #6438
Conversation
…go and change runOn to platform
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
Kudos, SonarCloud Quality Gate passed!
|
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.
Added a few comments. I also noticed that there were a few changes related to #6437 (odo delete component --name
on Podman). Can you rebase this branch onto main
instead?
@@ -31,7 +31,7 @@ Learn more about the experimental mode in [this doc](../docs/user-guides/advance | |||
<iframe width="560" height="315" src="https://www.youtube.com/embed/EmN_hGkOHX4?list=PLGMB2PY4SNOr5pjbPTdcWsIrOezCPXWdX" title="odo dev using podman" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> | |||
|
|||
You can now use`odo dev` to run your application on Podman. `odo` leverages the benefit of Podman to work seamlessly with Kubernetes YAML and replicate them to containers locally. | |||
This is an experimental feature and can be used with `--run-on` flag. | |||
This is an experimental feature and can be used with `--platform` flag. |
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 think we should keep run-on
in this blog post, as it is specific and relevant to 3.3.0
@@ -9,7 +9,10 @@ type ComponentAbstract struct { | |||
RunningIn RunningModes `json:"runningIn"` | |||
Type string `json:"projectType"` | |||
// RunningOn is the platform the component is running on, either cluster or podman | |||
// This field is deprecated and will be replaced by Platform | |||
RunningOn string `json:"runningOn,omitempty"` |
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.
Can you also mark this field as deprecated with the // Deprecated:
comment?
// GenericRunOnFlag is the feature supporting the `--run-on` generic CLI flag. | ||
GenericRunOnFlag = OdoFeature{ | ||
// GenericPformFlag is the feature supporting the `--platform` generic CLI flag. | ||
GenericPformFlag = OdoFeature{ |
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.
A few characters missing here - I think you meant GenericPlatformFlag
;-)
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.
One last comment. Can you also update the following occurrences accordingly?
$ git grep 'run-on' -- ':!docs/website/blog' ':!vendor'
tests/integration/cmd_devfile_list_test.go: It("should display component depending on experimental mode and run-on flag", func() {
tests/integration/cmd_devfile_list_test.go: By("returning component not in dev mode when experimental mode is enabled with json output and run-on is cluster", func() {
Closed in favor of #6445 (based on main instead of branch) |
What type of PR is this:
/kind feature
What does this PR do / why we need it:
--run-on
flag with--platform
odo list component
runningOn
withplatform
field in JSON output ofodo list component
and deprecaterunningOn
Which issue(s) this PR fixes:
Fixes #6318
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: