Skip to content
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

endPoint field in ocm-provider json should be camelCase? #1752

Closed
michielbdejong opened this issue Jun 1, 2021 · 2 comments
Closed

endPoint field in ocm-provider json should be camelCase? #1752

michielbdejong opened this issue Jun 1, 2021 · 2 comments

Comments

@michielbdejong
Copy link
Contributor

On http://localhost:19001/ocm/ocm-provider/ I see:

{
   "enabled": true,
   "apiVersion": "1.0-proposal1",
   "host": "localhost",
   "endpoint": "https://localhost/ocm",
   "provider": "cernbox",
   "resourceTypes": [
      {
         "name": "file",
         "shareTypes": [
            "user"
         ],
         "protocols": {
            "webdav": "/cernbox/ocm_webdav"
         }
      }
   ]
}

but my code is looking for endPoint, not endpoint.

[Question to self:] Is this part of OCM documented somewhere?

@michielbdejong
Copy link
Contributor Author

Looking at cs3org/OCM-API#37 it was suggested as camelCase, but apparently this didn't make it into https://github.com/cs3org/OCM-API/blob/develop/spec.yaml#L33.

michielbdejong pushed a commit to michielbdejong/ocm-stub that referenced this issue Aug 6, 2021
michielbdejong added a commit to michielbdejong/reva that referenced this issue Oct 6, 2021
@glpatcern
Copy link
Member

This was fixed in one of the last PRs around OCM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants