-
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
add breaking changes in odo 2.2 doc #4683
add breaking changes in odo 2.2 doc #4683
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: girishramnani 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 |
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.
Some quick suggestions. Can be committed right away through GH interface, AFAIK.
|
||
It won’t fail in the sense that if you tried the conventional s2i approach and try to create odo url create it would fail with url for 8080 port already present as there would already be one for you. issue - #4621 | ||
|
||
* Is odo env --now and odo delete --wait permanent or temporary as we already have the issue for “normal” devfile components |
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.
* Is odo env --now and odo delete --wait permanent or temporary as we already have the issue for “normal” devfile components | |
* Is `odo env --now` and `odo delete --wait` permanently disabled or temporarily as we already have the issue for “normal” devfile components |
Co-authored-by: Dharmit Shah <shahdharmit@gmail.com>
Co-authored-by: Dharmit Shah <shahdharmit@gmail.com>
Co-authored-by: Dharmit Shah <shahdharmit@gmail.com>
What type of PR is this?
/kind documentation
[skip ci]
What does this PR do / why we need it:
see $SUBJECT
Which issue(s) this PR fixes:
Fixes #4281
PR acceptance criteria:
Unit test
Integration test
Documentation
I have read the test guidelines
How to test changes / Special notes to the reviewer: