Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Delegue Alexandre
    @larousso
    ok thanks I will try that
    Søren Valentin Silkjær
    @SoerenSilkjaer
    Thanks alot!
    Delegue Alexandre
    @larousso
    @sorenvalentinjp I ve reproduced the problem and I’ve fixed it, a new release is coming soon
    Delegue Alexandre
    @larousso
    The new client should be published
    Søren Valentin Silkjær
    @SoerenSilkjaer
    That is awesome! I will try it out asap and report back to you
    Delegue Alexandre
    @larousso
    Cool ! 😎
    Søren Valentin Silkjær
    @SoerenSilkjaer
    Good news! It works!
    Delegue Alexandre
    @larousso
    Good, it was a fucking nightmare I don’t really know how I solved it …
    That ’s great if that works !
    Søren Valentin Silkjær
    @SoerenSilkjaer
    Well done, sir 🙂
    Dragan Raicici
    @DraganRaicici
    @larousso Thanks for looking into and fixing the problem! Good job!
    thomasblok98
    @thomasblok98
    Hi :) Is there any way to setup the API-keys to be read-only? We are trying to use Izanami from Angular project, so we are wondering if we can call the API without exposing the key and without setting up a proxy as you suggested in the documentation?
    Mathieu ANCELIN
    @mathieuancelin
    Maybe you can use it with an Otoroshi instance to handle api key
    Otoroshi can issue read only apikeys
    Mathieu ANCELIN
    @mathieuancelin
    still, I don't think it's a very good idea as it leaks too much informations
    Klaus Hebsgaard
    @khebbie
    Hi I am with Thomas Blok - @mathieuancelin how would you then recommend using izanami with angular?
    or would you maybe recommend that we do not use izanami with angular?
    Søren Valentin Silkjær
    @SoerenSilkjaer
    @larousso Do you have any experience on this matter?
    Mathieu ANCELIN
    @mathieuancelin
    @khebbie of course you can use izanami with an angular app, or any js app
    but we don't recommand using the api directly from the client app
    to avoid leaking too much information, like the izanami host, the path of the features, the apikeys, etc ...
    we recommand using a backend for frontend pattern
    Mathieu ANCELIN
    @mathieuancelin
    but of course you can do whatever you want :) nothing prevents you to use izanami directly from your angular app
    and you can use Otoroshi to handle same host issues, cors issues, read only apikeys, etc ...
    Søren Valentin Silkjær
    @SoerenSilkjaer
    Is there a way to not send Configuration SSE events to Izanami Feature Clients when using smartCacheWithSSE strategy? Our issue is that these Configuration events exceed some akka http sse event size limits, which throws errors in all our feature clients. Most of our apps are only using features, so it would be awesome to not receive other events.
    Søren Valentin Silkjær
    @SoerenSilkjaer
    We decided to use a different strategy, so we wont have to bother with the akka sse events limitations.
    Delegue Alexandre
    @larousso
    Hi, I could update the client to choose only one domain
    Søren Valentin Silkjær
    @SoerenSilkjaer
    What is domain in this situation?
    jonaskoelker
    @jonaskoelker
    Is the Izanami client v1.7+ available for scala 2.12 and lower? Is that on the drawing board? I could not find any downloadables, yet the build.sbt says to cross-compile.
    Sven
    @ThatScalaGuy
    Hi, someone was able in the past to setup oauth2 with google as an identity provider?
    Søren Valentin Silkjær
    @SoerenSilkjaer
    Is there a way to filter out bot traffic in izanami experiments?
    Amitg1
    @Amitg1
    Hello, what is the relationship between feature and experiment? and how can I retrieve allocation? ( assignment to group A/B)
    Søren Valentin Silkjær
    @SoerenSilkjaer
    Hi. @Amitg1. I dont think there is a relationship between the two, they are decoupled.
    Retrieving the experiment variant for a client is well documented in the Izanami documentation. https://maif.github.io/izanami/manual/experiments/index.html
    Amitg1
    @Amitg1
    What about non-overlapping tests? does the platform has this kind of feature?
    Søren Valentin Silkjær
    @SoerenSilkjaer
    You can configure an experiment to run within a date range. For example experiment "A" is active from today until tomorrow and experiment "B" is activated from tomorrow until the day after tomorrow.
    Amitg1
    @Amitg1
    yes, but question is if I can create both of these experiments and somehow allocation users only to one. like facebook's planout namespaces (https://facebook.github.io/planout/docs/namespaces.html)
    Søren Valentin Silkjær
    @SoerenSilkjaer
    Ahh. I think I understand. That is not supported in Izanami
    You would have to keep all the variations in one single experiment, but I don't think that is what you want
    Amitg1
    @Amitg1
    yes, it's not what I want. thank you for your answer
    Amitg1
    @Amitg1
    @SoerenSilkjaer is the project still in maintenance?
    Jonas Kölker
    @jonaskoelker-jypo
    In izanami-server/app/domains/feature/instances.scala in DateRangeFeatureInstances.isActive I see val now: LocalDateTime = LocalDateTime.now(ZoneId.of("Europe/Paris")). I'm not sure why the timezone is hard-coded. I would think it should be configurable. I'm sure I don't know all the context; am I missing something?
    Delegue Alexandre
    @larousso
    Hi, at the moment it's hard coded, we could add it to the config
    Open an issue and we'll do it
    Søren Valentin Silkjær
    @SoerenSilkjaer
    Does Izanami support json logging? It is very difficult to read the logs in our logging infrastructure, because the current logger logs one event per line and that is really built for consoles.
    Delegue Alexandre
    @larousso
    logstash-logback-encoder is on the classpath so you could use it in the logback config
    Rune Hjertsted Jørgensen
    @RuneJorgensen
    Hi :)
    We're thinking about making a separate Izanami proxy, to handle calls from our various clients that need to interact with our Izanami server. We do have BFF's for our frontend clients, but replicating the proxy code across several BFF's seems like a bad move, so that sparked the interest in making a shared proxy.
    Does anyone have any experience making a proxy for Izanami. Do's and Don'ts. Other ways to solve the underlying problem?
    Thanks
    Mathieu ANCELIN
    @mathieuancelin
    @RuneJorgensen in the latest version of otoroshi, there is an izanami proxy plugin to do exactly what you need ;) https://github.com/MAIF/otoroshi/blob/master/otoroshi/app/plugins/izanami.scala
    this plugin will expose a /api/izanami path (you can define your own path) that will expose the subtree you need. it handles apikey and patterns for you
    Dragan Raicici
    @DraganRaicici
    Hi everyone! :)
    The latest release of Izanami, 1.8.4, has an interesting name attached to it, namely "Release v1.8.4 KO don't use it". I assume we have to wait for v1.8.5 instead?