Merge meta.yaml and devfile.yaml

[GeekArthur]

Signed-off-by: jingfu wang [email protected]

Fixes devfile/api#172

This PR is used to move fields from meta.yaml to devfile.yaml in terms of documentation.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: GeekArthur
To complete the pull request process, please assign after the PR has been reviewed.
You can assign the PR to them by writing /assign in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[johnmcollier]

I think these changes need to be made in the github.com/devfile/api repo? As this json file is copied automatically from the generated json spec each time changes are merged into devfile/api

[GeekArthur]

I think these changes need to be made in the github.com/devfile/api repo? As this json file is copied automatically from the generated json spec each time changes are merged into devfile/api

I think the changes for devfile.json in this repo is only for documentation, basically what is does is to guide the docs generator to generate the html files so that the new devfile schema can be deployed and displayed on our public website.

[GeekArthur]

@johnmcollier https://github.com/devfile/docs/blob/master/generate-api-reference.js#L12 here is the place how this repo uses the devfile.json that we change.

[johnmcollier]

@GeekArthur This CI job https://github.com/devfile/api/blob/master/.github/workflows/ci.yaml#L66 publishes the devfile.json to this repository whenever the devfile schema has been modified, so any changes in here would get overwritten whenever the job is run.

If you're adding new fields to the metadata field of the devfile spec, wouldn't we need to deliver the changes to https://github.com/devfile/api/blob/1103496bda97425017e4f7fb01e4896ecfa2b5d8/pkg/apis/workspaces/v1alpha2/devworkspace_types.go#L73

[GeekArthur]

@GeekArthur This CI job https://github.com/devfile/api/blob/master/.github/workflows/ci.yaml#L66 publishes the devfile.json to this repository whenever the devfile schema has been modified, so any changes in here would get overwritten whenever the job is run.

If you're adding new fields to the metadata field of the devfile spec, wouldn't we need to deliver the changes to https://github.com/devfile/api/blob/1103496bda97425017e4f7fb01e4896ecfa2b5d8/pkg/apis/workspaces/v1alpha2/devworkspace_types.go#L73

Ah, I was missing the CI part in API repo, I am gonna make the changes on API repo, thanks for pointing that out.

[GeekArthur]

The changes need to made on API repo as the API repo CI is responsible for syncing the devfile.json.