GitLab Speed Runs, 17 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Speed run for setting Feature Flag strategy across environments

Description

https://gitlab.com/gitlab-org/gitlab/issues/35555
https://docs.gitlab.com/ee/user/project/operations/feature_flags.html#create-a-feature-flag

A

Morning, everyone, my name, is Jason navorski and I'm. The product director for CI CDI, get lab, and today I want to record a blind speedrun of a feature that literally was just released, and so this is up on the preview page for the 13.1 release, which will be releasing on the 22nd of this month. But when it's here it means that it was deployed to be lab comm already so I'm gonna give it a try there and I'm. Let's open up the docks and see what we've got.

A

I am doing this totally blind, so it'll just kind of be like it's a real new user experience. Okay, so looks like all you do. Is the docks just link to creating a feature flag to creating your feature flag. um It doesn't really talk about the strategy here, but maybe it will become more clear when we actually try it on so, let's go make a project alright, so.

A

Jack's project and then we'll call this pitch bike test: Oh public initialize it with a readme I. Don't think we actually gonna need to do anything in source, so I won't do like a full and end test where we change the future flag, but I'll just try creating one that has the strategy and then I'll try adjusting the strategy and see what happens. Okay,.

A

Okay, so it does look like we need some environments, so it's gonna environments here create a new environment, we'll call woman perfection.

A

And make no one called.

A

hmm And then maybe make one more call tests I'm, not exactly sure how it will be is but okay, so alright. Now each operation feature flags.

A

And create any feature flag and then it starts the letter names only lowercase, yeah sure.

A

So that cool new feature, okay, then here's the new strategies, I suppose enable features for specific users and specific environments by defining feature flag strategies by default. Features are available to all users in all environments: okay, cool.

A

So all users in the environment, production, let's say oh this means all users get it I. Think.

A

Yeah, maybe as different name here, would be more clear, I think, but I do think what this means is that it's on by default or on for everyone is maybe a better way to put it percent rollout for logged in users, user, IDs and lists.

A

How would I do percent rollout if I want to just do for all users? Maybe it's not possible now, okay, so you got production percent. Rollout, let's say stage is currently at 0 as well.

A

And then how do I add and how do I add a third strategy, though ok, there we go and then let's say we want on for all users in our test: environment, ok, cool, that's pretty clear, barring minor minor issues that I mentioned.

A

Ok, hmm it's not really showing me much about I would have expected there to be something here in environments but because I just set up some things about environments, but it does look like.

A

Yeah, so it looks like nothing is shown on this overview, but I think that that's actually really important data. So maybe we already have a follow up to add this, but either way I would I think that we should probably move the strategies there and I actually wonder what this is even referring to you, because I didn't see any way to set environment specs anymore.

A

So maybe maybe that's just a mess or maybe I'm missing something as to why that's blank on the other page I'm, not sure but I guess what you would do is that at this point is come in and then change this, maybe to example, so 50 percent, and then you do some testing.

A

Yes, I really do miss seeing it there. Then you change this to you. Maybe all users, and then you kind of just you know, roll out your feature in this way, which is really cool, and then you can say well we validated it in stage we validated it in test so now we'll just turn it on for everybody in production and and be happy yeah, really cool and I assume that there's like audit logs for for all of those things happening no.

A

hmm Yes, I'm, probably audit logs for changing changing feature flag, because this is essentially what we're doing here is a change, a production change, so those should be recorded but yeah anyway, that's my feedback, nice new feature and yeah. Hopefully this is helpful for anybody who's interested in checking it out. Thanks for watching.