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

Question about registry versioning #1398

Closed
kcheenu opened this issue Mar 31, 2021 · 12 comments
Closed

Question about registry versioning #1398

kcheenu opened this issue Mar 31, 2021 · 12 comments

Comments

@kcheenu
Copy link

kcheenu commented Mar 31, 2021

Do apicurio-registry support custom versioning ? Can the control of versioning be customized ? If so can you please help by giving the pointers ? Thanks.

Regards,
Srini

@carlesarnal
Copy link
Member

Hi @kcheenu. We've introduced this feature in our 2.0 release. Basically, whenever an artifact or artifact version is created, you can specify/override the version by sending the X-Registry-Version HTTP request header. The value can be a string. From then on, you can use that version value when executing any operation that requires it.

@kcheenu
Copy link
Author

kcheenu commented Mar 31, 2021

Thanks carlesarnal. I tried by providing the registry-version in version 2.0 but still it is not picking the version which i'm passing.
For example below is my http header
content-type: application/json
cookie: e93476e7f1cdab5a19e47be7e3f00e18=c346a568db8736bde01816f5ba9bc2c8; e51ba8f75e96518c01facdf5b9aa13f1=961d71e33fbcd1c87c1a22123dd83820
accept: application/json
accept-encoding: gzip, deflate
accept-language: en-US,en;q=0.8
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Safari/537.36
X-Registry-Version: 1s

and I'm calling the Create API - POST /artifacts when I go through the UI I'm still getting the version as 1.

we are using https://hub.docker.com/r/apicurio/apicurio-registry-sql/tags?page=1&ordering=last_updated
in that 2.0.0.RC1 TAG - apicurio-registry-sql:2.0.0.RC1

Any pointers is highly appreciated.

Regards,
Srini

@carlesarnal
Copy link
Member

Sorry @kcheenu, this feature is not part of 2.0.0.RC1, will be part of the final release.

@amalkurup89
Copy link

@carlesarnal what is ETA for final release version

@kcheenu
Copy link
Author

kcheenu commented Apr 5, 2021

@carlesarnal Any planned release date for 2.0 final release ? Appreciate your response if you have. Thanks.

Regards,
Srini

@EricWittmann
Copy link
Member

The 2.0.0.Final release is scheduled for very soon... Hopefully by the end of this week.

@EricWittmann
Copy link
Member

Sorry for the delay responding to this. Trying to get a bunch of things done and finalized so we can do the release. :)

@kcheenu
Copy link
Author

kcheenu commented Apr 7, 2021

Thanks @EricWittmann for the update. Hopefully the custom version feature is also part of this final release and we are eagerly looking to use this feature.

Kind Regards,
Srini

@EricWittmann
Copy link
Member

Yes - I can confirm that the custom version feature will be included in 2.0.0.Final.

@kcheenu
Copy link
Author

kcheenu commented Apr 14, 2021

@EricWittmann any updates on 2.0.0 final version release date ? Earlier communication says last week but i couldn't see them as of today. Appreciate your response. Thanks.

Kind Regards,
Srini

@EricWittmann
Copy link
Member

The current plan is Friday of this week!

@carlesarnal
Copy link
Member

Closing since this feature has been released in 2.0.0.final.

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