Hello LakeFS Team, we have noticed some issues wit...
# help
k
Hello LakeFS Team, we have noticed some issues with tagging now that we have upgraded
lakectl
from
0.57
to
0.61
. Issue: We tag lakefs commits with
prefix-X.X.X
(i.e
test-1.0.0
). This does not seem to be working anymore. It seems that the hyphen/periods is now an issue. Version:
Copy code
lakectl --version
>> lakectl version 0.61.0
Command:
Copy code
lakectl tag create --config /root/.lakectl.yml --force <lakefs://origin/test-1.0.0> d8d8a9974512c34bd526823e46447ed89488e4e749965f3462ab5dd60dbdd013
Error:
Copy code
Invalid tag: not a valid ref uri
Any help would greatly be appreciated.
y
Hey @Koonal Bharadwaj, welcome to the community! You are right. There indeed is a bug in the tag name validation. It will be fixed in this PR, which will be merged very soon. Let me suggest a workaround for you, until the next lakeFS version is available.
🙌 1
👍 1
🐛 1
k
Hey @Yoni Augarten, that's great. Thanks.
y
For this to work, you can use a tag name without
.
in it. This will pass the current validation. On the next version you will be able to re-tag the same commits with your desired tag name.
So for example, you may use "test-1-0-0" as a temporary tag.
However, there has been another breaking change in a recent release.
k
👍, sounds good. I'll use the workaround for now until the next patch release of LaekFS. Thanks man!
🙏🏻 1
y
It happened on this PR. The implication is that you will have to use a full lakefs URI instead of just the source commit ref when creating a tag.
So your final command would be:
Copy code
lakectl tag create --config /root/.lakectl.yml --force <lakefs://origin/test-1-0-0> <lakefs://origin/d8d8a9974512c34bd526823e46447ed89488e4e749965f3462ab5dd60dbdd013>
👍 1