-
Notifications
You must be signed in to change notification settings - Fork 23
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 quick start guides for new adopters #87
Add quick start guides for new adopters #87
Conversation
☁️ Nx Cloud ReportAttention: This version of the Nx Cloud GitHub bot will cease to function on July 1st, 2023. An organization admin can update your integration here. CI is running/has finished running commands for commit e52a584. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 5 targetsSent with 💌 from NxCloud. |
1a4628e
to
49a821f
Compare
Might be a good idea to provide link to Sandbox and also instructions to Che setup |
0a41523
to
0c38652
Compare
Waiting on reviews from members of odo and Eclipse Che teams. |
4. Create a devfile with the filename `.devfile.yaml`. Add the [`schemaVersion`](./devfile-schema#schema-version) field with the desired devfile specification version to use | ||
|
||
```yaml {% filename=".devfile.yaml" %} | ||
schemaVersion: <version> |
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.
if we are showing snippets of the devfile content, it might be better to make it easier for users and include the actually version
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.
if we are showing snippets of the devfile content, it might be better to make it easier for users and include the actually version
It will include the actual schema version, <version>
is a placeholder for printing the selected schema version dynamically in that spot. So if you load the site under the 2.2.0
doc pages, <version>
will be replaced by 2.2.0
.
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.
oh, did not know that. That is really smart 👍
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.
In general, the Eclipse Che portion is somewhat out of date with current/upcoming releases. I'll share this PR with the team for more detailed review.
5. Go to 'Edit the workspace' and view the devfile. The devfile should be populated with content similar to the following | ||
- The `schemaVersion` of the devfile should be left to what Eclipse Che supports, currently `2.1.0` | ||
- The `metadata.namespace` field is the target namespace your project will be deployed in, for our current intent and purposes this can be left alone |
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.
This step will not work in Eclipse Che -- eclipse-che/che#22115. I believe the plan going forward is to allow editing the devfile from within the workspace itself (using the Code editor, for example) but I'm not 100% sure of the status of this feature.
Also, to add, Che currently uses devfile 2.2.0 schema -- the display in the edit page is a bug.
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.
This step will not work in Eclipse Che -- eclipse/che#22115. I believe the plan going forward is to allow editing the devfile from within the workspace itself (using the Code editor, for example) but I'm not 100% sure of the status of this feature.
Also, to add, Che currently uses devfile 2.2.0 schema -- the display in the edit page is a bug.
Thanks for your review @amisevsk!
Seems like the version of Eclipse Che under Red Hat Dev Spaces is an older version that is still on devfile spec 2.1.0
, I will need to write up revised draft for the current 2.1.0
guide as well as a new guide under 2.2.0
to cover the up to date content: devfile/api#1057 (comment)
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.
Seems like the version of Eclipse Che under Red Hat Dev Spaces is an older version that is still on devfile spec
2.1.0
, I will need to write up revised draft for the current2.1.0
guide as well as a new guide under2.2.0
to cover the up to date content: devfile/api#1057 (comment)
Update: devfile/api#1057 (comment)
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.
Update: devfile/api#1057 (comment)
@amisevsk I need a review of the recent changes when you are able to, thank you.
Signed-off-by: Michael Valdron <[email protected]>
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.
@michael-valdron the Devfile with Eclipse Che getting started article is really nice 👏
container component revisions: * rename 'runtime' to 'dev-tooling' * change image tag 'ubi8-latest' to 'latest' Co-authored-by: Mario Loriedo <[email protected]> Signed-off-by: Michael Valdron <[email protected]>
expand description of `universal-developer-image` to add more context to why Eclipse Che uses it Co-authored-by: Mario Loriedo <[email protected]> Signed-off-by: Michael Valdron <[email protected]>
reword opening to defining commands in Eclipse Che to improve clarity of why it is done Co-authored-by: Mario Loriedo <[email protected]> Signed-off-by: Michael Valdron <[email protected]>
revise 'id' description to not refer to it as a 'label' to avoid confusion with the 'label' field Co-authored-by: Mario Loriedo <[email protected]> Signed-off-by: Michael Valdron <[email protected]>
8dea25a
to
1e6a67f
Compare
remove incorrect note about execution order of commands, Eclipse Che executes commands individually with the user manually triggering them Co-authored-by: Mario Loriedo <[email protected]> Signed-off-by: Michael Valdron <[email protected]>
Signed-off-by: Michael Valdron <[email protected]>
…it replaced with a guide from the Eclipse Che documentation for getting started with 'Eclipse Che hosted by Red Hat' Signed-off-by: Michael Valdron <[email protected]>
Signed-off-by: Michael Valdron <[email protected]>
93d43b2
to
f526fdd
Compare
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.
👏 LGTM
…the new developer persona. Signed-off-by: Michael Valdron <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kadel, l0rd, michael-valdron, mike-hoang 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 does this PR do / why we need it
Create quick start guides for writing devfiles using odo v3 and Eclipse Che. This is to give the new adopter a practical exercise for learning how to write a simple devfile.
Additional changes
hotReloadCapable
attribute description in the spec has updated the comments in the spec modelsWhich issue(s) does this PR fix
Fixes #?
fixes devfile/api#1057
PR acceptance criteria
Update the sidebar if there is a new file added or an existing filename is changed
How to test changes / Special notes to the reviewer