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

Create artifacts for rest-api-spec #702

Closed
naveentatikonda opened this issue Oct 6, 2021 · 5 comments
Closed

Create artifacts for rest-api-spec #702

naveentatikonda opened this issue Oct 6, 2021 · 5 comments

Comments

@naveentatikonda
Copy link
Member

naveentatikonda commented Oct 6, 2021

We are trying to fetch the updates in apis from the rest-api-spec into OpenSearch-Specification and many clients(like opensearch - js). We are doing it manually as the artifacts are not yet created. Can we create the artifacts for rest-api-spec like "rest-resources-zip-7.15.1.zip" in https://artifacts-api.elastic.co/v1/versions/7.15

Here is an example to show where it is being used:
https://github.com/opensearch-project/opensearch-js/blob/main/scripts/download-artifacts.js#L117

They just added the url something similar to how elasticsearch added it but it needs to be updated once the url is finalized.

@gaiksaya
Copy link
Member

Hi @nknize , @dblock are we building, publishing these artifacts today? https://github.com/opensearch-project/OpenSearch/tree/main/rest-api-spec
How will the customer download the generated zip, is it using distribution downloader or any specific https location is good?

@VijayanB
Copy link
Member

VijayanB commented Oct 22, 2021

We should have a manifest file (hosted as service) which lists all different product/version, and url from where we can download.
For ex: opensearch-* clients will be running CI against every new release (including snapshot) of opensearch rest api .

@gaiksaya gaiksaya added the untriaged Issues that have not yet been triaged label Dec 10, 2021
@zelinh
Copy link
Member

zelinh commented Dec 16, 2021

[Triage] We need more information from core team and @naveentatikonda on this one.

@zelinh zelinh removed the untriaged Issues that have not yet been triaged label Dec 16, 2021
@naveentatikonda
Copy link
Member Author

@zelinh This is on hold right now.

@gaiksaya
Copy link
Member

gaiksaya commented Dec 16, 2021

@naveentatikonda Closing this now. Please create new one with specific requirements and usecase from your end.
Please reopen if you think otherwise.
Thanks!

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

4 participants