GitLab Support Operations, 22 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Adding a SKU to the ZD-SFDC sync

Description

Adding a SKU to the ZD-SFDC sync

A

Okay, hey, so um we have a new SKU being added gitlab for non-profits, so we need to update our sleep scripts to account for that so I figured we'd. Do a quick pairing on how I do those so we're in our projects?

A

Here's the zoom thing all right! So we're in our projects. um What I traditionally would do is go into the Salesforce dot RV file, because that's where we sync from Salesforce and you'll notice. We have this wonderful check plan by blah blah I think, okay, so we have that and we have cr. So we have two of them: okay, so you'll notice. We have a couple of these Community ones, because something like this would definitely be a community they're not entitled to support.

A

So we just need to return the community if sub dot plan name seed is equivalent to that.

A

A

All right, so um that's what we would need to add there we're going to copy this and go down to our other. It's not a good thing. I saved it there we go all right, so we're going to copy that and go down to our other check plan for Zoo Aura sub.

A

You notice this doesn't really have the community stuff. It's because it's going to be a customer sub, not a sports sub, but if we wanted to be thorough we could also add it here.

A

I, don't know why I'm taking all that out when I copied it could do it here. We don't really need to worry about that. One though, because there's not going to be a subscription for it, so let me just get rid of that, but the key thing here is looking at what would the plan be in zendesk so in this case Community right, because it's Community sub they're not entitled to support, so we need a return Community. If the plan name is gitlab for non-profits foreign.

A

And we want to make sure it's at the top that way. There's none of these other ones catch because you'll notice, it's return or term return return. It'll! Stop this function immediately.

A

So we want to add the community stuff at the top, because if it catches this stuff first for the plan name, it's done. It doesn't matter what else it says like it could say, edu program gold plan, but it's still edu program. So this is still the principal thing it's a matter of which one takes priority. So in this case it says gitlab for non-profits. We want it to you community.

A

The reason we do the regex for it instead of just saying equals equals is because they could do Bob's, Burgers Dash get lab for nonprofits and at which point, if we did an equal equal, it would not catch it and it would continue going through all these other ones and ultimately, it ended up at custom because it's not going to match anything else or they could do. You know gitlab for nonprofits Dash gold plan. Well, it's not a gold plan.

A

It's a community plan, so we want to make sure we catch it that way we don't want to be dependent on it, always saying that we do want the regex to be specific enough, though, that we catch it because if I just did non-profits okay, but if we have a company, actually pay us for a you know ultimate plan and their name is non-profits for you.com or something we don't want that getting caught.

A

Obviously, if a company files their name as edu or OSS, we might have a problem, but I figure across that bridge when we get to it.

A

So that's pretty much all we need. You can go ahead and copy our Branch here do a get checked out. Dash B, we're going to add. We should always remove cop make sure it goes through everything. Yeah, there's, probably a couple things that need to be fixed, but nothing blocking so we're just going to keep moving. You can always come back later and clean up all right.

A

So we'll add it and we'll add a commit message uh counting before get lab or non-profit SKU I know I'm so original, and then we're going to push it to our Branch I'm, real bad about remembering what branch I'm on so continue to do that get flash origin two.

A

And the get lab UI is nice and early. Get lab return. Is nice enough to give me an MR or pre-filled in our link? Okay. So if you choose what it should be linked to confirm that cool this link there, our title is good: there's not a corresponding support team meta, I'm, the manager so I'm going to just remove that, because I don't need my own review.

A

um I would normally link the support team that F1 exists but related. What this links back to is a finance issue, so I'll link that and we're gonna give it a normal priority and we're gonna give it a support exchange.

A

um Give it a change three. uh Given the lightness, it's not going to hit the students so we'll change our Milestone to the following month, because we're definitely with a change through. Even though it's a one week notice, it's the 20, well I! Guess with the 22nd we could make it I would say: normally we have whoever's going to deploy it make that decision. So what do you think Sarah I think it'll be ready for deployment by the end of the month.

A

I think we're. Okay, all right, then we'll keep it down, keep it in draft mode, because we want to review it first, make sure it's closing that always make sure these two boxes are checked. Click, merge, requests.

A

All right, so we got that done. We got all our labels check our changes, real, quick, just to make sure to store, reflects what we wanted. Yep there. It is, and at that point the other person, your other dri, so Sarah would review it and we'll go from there and then determine our deployment date with the change three. We only really need a week's notice, so we'll probably review it today and then announce sometime today when it'll be deployed and then we'll merge it and all that fun stuff.

A

So yeah we'll go ahead and stop the screen share. um That's that's! Really. All there is to adding skus, especially one that is so very straightforward as such as gitlab for non-profits.

A

um They can get complicated depending on naming and other stuff, so you tend to have to review what the other settings are and kind of determine. How do we want this to fit in the priority order? How do we want this to the red eyes? Something that you know like I give the example of edu gold plan. Well edu is what it really is, so it's community. So we want that towards the top, um but something like paid edu gold plan.

A

We might want to actually catch the gold plan, so we would want to make sure our other statements don't contradict that. So it's kind of a matter of looking at what the SKU is going to be what its name is. Occasionally, you might have to make sure you know confirm with Finance of hey 100. This is the name, because that's what we're actually using to determine all that.

A

But that's all there really is to having a skew to the sync script for Global. Federal is not too much different. The reason we don't bother with Federal is there's other criteria to get into Federal, and these this specific SKU will never hit us Federal. So there's not really a point in updating that we could it's just going to be a condition.

A

That'll never be hit because you know there's other conditions to get the US Federal, but in reality that's all we really have to do and then moving forward to seeing script will you know handle that as they come, but any questions on that overall process super easy. So the key things for this will be um right. Now they ping me I'll, probably also have them ping you moving forward and they'll ping, us she's, saying: hey we're adding a new SKU.

A

We just confirm: hey confirm this is the name and then we go do the code changes that we need to do and try to get it deployed in time for whatever they're doing never hurts to have it deployed beforehand hurts a lot to have it deployed after so we always aim to do it beforehand, cool um any general questions. Anything you want to know any of that stuff all right. Well, then, we'll continue moving on that Mr, but thanks for joining I hope you found it. Educational.