Thanks, Sergii
A couple questions inline
Thanks
Hello
I would like to share some notes from the meeting that was on last Friday about Devfile implementation
https://github.com/eclipse/che/issues/11549- For now, we would like to position Devfile as workspace configuration. We don't want
to embed Devfile as some field of workspace configuration.
Could you please elaborate a bit what does "embed Devfile as some field" and why it may be the case to consider "after" (since you mentioned "for now")?
By this "embed Devfile as some field" I meant something like this:
"devfile": {
"type": "devfile",
"content": "Content of devfile"
"parameters": {}
}
>and why it may be the case to consider "after"
Depending on the success of Devfile we may or may not revise our workspace model for Che 8 or later.
- In the beginning, we would like to make some assumption to simplify implementation.
We will consider that Devfile can be on public GitHub repositories. We can consume HTTP link to Devfile or content of Devfile itself.
How GitHub based HTTP GET accessible URL differs from others? I.e. can we consider this file to be located in ANY accessible place not only inside GH repo?
HTTP link can be to any server that does not require authentication. git url can be to GitHub public repositories only.
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev