Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Referenced url not found #81

Open
nab-gha opened this issue Jul 18, 2022 · 4 comments
Open

Referenced url not found #81

nab-gha opened this issue Jul 18, 2022 · 4 comments
Labels
kind/bug Bug lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@nab-gha
Copy link

nab-gha commented Jul 18, 2022

What happened:
Tried to access url at https://github.com/gardener/component-spec/blob/master/language-independent/component-descriptor-v2-schema.yaml#L1 but got 404

What you expected to happen:
Return a document describing yaml
How to reproduce it (as minimally and precisely as possible):
cut and paste url https://gardener.cloud/schemas/component-descriptor-v2 to browser.

Anything else we need to know:
Same reference at https://github.com/gardener/component-spec/blob/master/doc/proposal/component-descriptor-v2-schema.yaml#L1
Environment:

@nab-gha nab-gha added the kind/bug Bug label Jul 18, 2022
@nab-gha
Copy link
Author

nab-gha commented Jul 18, 2022

Now reading the README.md again, these files relate the the existing CNUDIE and not OCM specification so this is not an OCM issue. Should we separate the OCM specification documentation and artefacts into a separate repository to avoid confusion and allow us to develop the new OCM specification documentation and examples ready for wider publication.

@In-Ko
Copy link
Contributor

In-Ko commented Jul 19, 2022

I think it is a good idea to clearly separate the two (CNUDIE and OCM) specifications / documentations and artifacts. Should we have a repo like "gardener/ocm-spec" or similar ? Or simply move everything now under the existing "gardener/ocm" repo (internally structured via folders for example), as we will move to the "real OCM home" anyhow at a later point in time ?

@nab-gha
Copy link
Author

nab-gha commented Jul 19, 2022

I'd support gardener/ocm-spec which might one day become ocm/spec, I think moving it into the existing gardener/ocm would be ok but better to have a separate repo for the spec and the cli.

@In-Ko
Copy link
Contributor

In-Ko commented Jul 21, 2022

ok, so we go for a separate gardener/ocm-spec repo, will also make it easier later on to move all those "ocm" repos under a new org. So then we should:

  • create a new "ocm-spec" repo
  • move the whole "proposal" folder from this repo ("component-spec") repo to that new repo

I am aware of at least one PR that still needs to find its way to the proposal spec in this repo ("component-spec"), so we have to wait until this is done, and then we can do the move.

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Jan 17, 2023
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Sep 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Bug lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

3 participants