https://www.ory.sh/ logo
Join Slack
Powered by
It will be deleted again once a proper release is ...
# talk-keto
s
It will be deleted again once a proper release is out
✅ 1
a
Cool, is there any plan on when this will happen?
s
Once everything passes 😅
a
Yeah that makes sense 😉 I was planning on migrating from 0.6.0 to 0.7.0, but it is a lot of effort with forced down time, so if possible I would like to immediately jump to 0.8.0. Is this more of an hours/days/weeks thing?
s
probably hours
at least I hope
but you can go to 0.7 first, as 0.8 does not need migrations (I think)
a
Perfect, thanks!
s
yeah no new migrations added since 0.7
🙌 1
or rather hope 😅
a
Hurray!
Fingers crossed 😉
Good morning! Pipeline seems to have been successful, but I don't see the new version released on nuget or npm, any ideas?
s
The pre release was successful, but the real release failed Working on it today
a
Cheers! Good luck
s
Ah so it was only the post-release task failing, the release is there: https://github.com/ory/keto/releases/tag/v0.8.0-alpha.0
But the SDKs will follow soon There were not too much changes in regards to the SDKs anyway
✅ 1
a
Hi Patrik! So I just released the SDKs were released a week or so ago. I noticed that the ActionEnum for patching code generation is broken.
Copy code
/// <summary>action</summary>
/// <value>action</value>
[JsonConverter(typeof (StringEnumConverter))]
public enum ActionEnum
{
  /// <summary>
  /// Enum InsertDelete for value: [[[[[[[[[[insert delete]]]]]]]]]]
  /// </summary>
  [EnumMember(Value = "[[[[[[[[[[insert delete]]]]]]]]]]")] InsertDelete = 1,
}
This is what got generated
Ah I just noticed you have already fixed this
s
yes, there was a problem with the spec generation
✅ 1
we could release again to fix the sdks
a
We have decided to stay on 0.7.0 for now, so this is not blocking us specifically
s
👍 there will be a release soonish anyways
a
Hi again! Don't mind me reusing this chat all the time 🙂
It seems that the ory keto helm chart does not work as intended
The liveness probes are still referring to the write api although there is now the metadata endpoint
s
What if I do mind? 😉 The metadata part of the API is actually not its own endpoint but on both read and write. This is just a way to make it possible to use the SDK on both endpoints. Sorry for the confusion, we will restructure the SDK soon to be easier to understand...
✅ 1
a
I see! Thanks for the quick reply
s
np
3 Views
Open in Slack
PreviousNext
Powered by