text stringlengths 0 2.29k |
|---|
[2260.12 --> 2262.08] Because it doesn't have to serve a lot of traffic. |
[2262.08 --> 2263.92] It doesn't need to be anything big. |
[2264.02 --> 2264.36] You don't have to. |
[2264.46 --> 2265.80] The CI CD is already there. |
[2265.90 --> 2271.14] You have a VM where you're running the actual code for your tests. |
[2271.56 --> 2278.34] So, why wouldn't you run a longer running process that exposes changelog? |
[2278.44 --> 2279.80] You're blowing my mind, Gerhard. |
[2279.92 --> 2280.36] I'm not even. |
[2280.36 --> 2281.44] That's a crazy idea, right? |
[2281.50 --> 2282.94] No one has thought about that before. |
[2285.22 --> 2285.80] All right. |
[2285.88 --> 2286.18] All right. |
[2286.30 --> 2287.04] See, I told you. |
[2287.08 --> 2287.88] Six months from now. |
[2288.00 --> 2288.84] It's the future. |
[2289.48 --> 2289.86] Okay. |
[2290.38 --> 2290.64] So. |
[2290.76 --> 2291.60] Well, that's exciting. |
[2291.60 --> 2301.46] When a pull request opens, basically, the GitHub runner that runs all the various checks, one of them, we basically, we don't, I mean, we keep it running for longer. |
[2301.46 --> 2303.58] Or we don't even use GitHub runners at that point. |
[2304.18 --> 2314.50] So, one of the things which we run, we spin up a changelog, a preview one, maybe, and we still need to figure out the data part, that will be accessible publicly. |
[2314.50 --> 2315.50] We get a random URL that you can't. |
[2315.50 --> 2319.50] We get a random URL that you can hit. |
[2319.50 --> 2321.50] And then you can connect to that instance. |
[2322.08 --> 2324.36] And that instance runs within one of the CI workers. |
[2324.36 --> 2330.26] When the pull request is merged, I mean, one of the checks, again, I still need to figure out how to do this. |
[2330.52 --> 2334.06] But one of the checks basically we will not finish until the pull request is merged. |
[2334.06 --> 2340.88] And that check in GitHub actions, that's the one where you can access the changelog, the preview version. |
[2341.78 --> 2342.00] Nice. |
[2342.32 --> 2344.48] So, literally, you're running a preview in CI CD. |
[2344.48 --> 2346.38] I'm going to need a new diagram. |
[2347.82 --> 2351.70] Infrastructure MD is the place to get our repo to see how everything wires together. |
[2351.86 --> 2355.08] And that's the one that I intend to update as we will have this new stuff. |
[2355.64 --> 2357.84] So, Infrastructure MD is fairly accurate right now. |
[2357.92 --> 2359.44] I think the only thing missing is GHCR. |
[2359.78 --> 2365.52] And the reason why it's missing is because I'm migrating the rest of the stuff to GHCR. |
[2365.88 --> 2369.52] And once that will complete, it will be weird to see both Docker Hub and GHCR. |
[2369.94 --> 2371.12] So, we're in a transition period. |
[2371.12 --> 2374.66] Once the dust settles, the diagram will be up to date. |
[2375.16 --> 2376.64] But again, that's the only thing which is missing. |
[2376.76 --> 2377.66] Everything else is accurate. |
[2378.50 --> 2381.90] Fly, Honeycomb, Sentry, everything. |
[2383.66 --> 2384.50] Very cool. |
[2385.72 --> 2386.42] Very cool. |
[2386.68 --> 2387.74] So, what about you, Jared? |
[2387.82 --> 2390.30] I know that you've had some improvements in mind. |
[2390.40 --> 2394.60] Some of them I think you've already done since Kaizen 8. |
[2395.32 --> 2395.76] Yes. |
[2396.52 --> 2397.74] Which one do you want to talk about? |
[2397.80 --> 2398.30] There's many. |
[2398.86 --> 2399.66] I can tell you that. |
[2399.66 --> 2405.78] So, a lot of my time, Gerhard, as you know, has been spent on rotating all of our secrets. |
[2406.20 --> 2407.22] Oh, my goodness me. |
[2407.32 --> 2408.02] We're so ready. |
[2409.98 --> 2412.78] So, LastPass, thanks for nothing. |
[2413.30 --> 2415.10] Well, thanks for a few good years. |
[2415.40 --> 2416.96] And then we've lost confidence. |
[2417.42 --> 2424.00] So, we are 1Password users as a team now, which we talked about for a few Kaizens. |
[2424.00 --> 2424.72] Mm-hmm. |
[2424.92 --> 2426.60] And finally made that migration. |
[2427.30 --> 2437.64] And then we decided, because of the LastPass leak and the fact that we're on 1Password now, it's like a great time to just go through and do a key rotation, right? |
[2437.64 --> 2441.76] Just rotate all of the things, which was just a lot of things. |
[2441.90 --> 2444.50] Like, man, we got a lot of secrets in there, lots of integrations. |
[2444.50 --> 2448.50] And mostly harmless. |
[2448.80 --> 2456.06] There's a few fallouts, as there tends to be, with just that many changes, things that went wrong because of that. |
[2456.64 --> 2471.36] The biggest one was our stat system went down for a few days because AWS credentials existed in one place correctly, but the other place incorrectly, I think. |
[2471.36 --> 2483.50] And then secondly, changelog nightly actually stopped sending because I didn't update the campaign monitor API key on nightly, which is an old digital ocean box from way back. |
[2483.78 --> 2487.76] Still just runs dutifully every night on a digital ocean box. |
[2487.82 --> 2495.44] So, I updated our campaign monitor API key inside of our app and in campaign monitor, but I didn't rotate it over on the other server. |
[2495.68 --> 2496.98] And so, it failed to send. |
[2497.08 --> 2500.54] It was still generating the emails, just not sending them, which is key. |
[2500.54 --> 2501.98] You know, that's a key part of it. |
[2502.34 --> 2505.26] So, there's like a few nights where nightly didn't go out until I realized it. |
[2505.30 --> 2507.50] And then I was like, oh, that one makes total sense. |
[2508.48 --> 2510.78] You and I also teamed up on a few things. |
[2511.08 --> 2511.60] Oh, yeah. |
[2512.06 --> 2512.84] Which is always fun. |
[2513.38 --> 2520.36] Issue 442, for anyone that wants to see all the things we had to go through, we had 79 tasks to complete. |
[2521.06 --> 2525.16] And some of them were quick, but just like untangling all that, we cleaned up a lot of stuff. |
[2525.16 --> 2527.96] And again, it was like almost like a spring clean, even though it was January. |
[2528.58 --> 2531.02] It was definitely spring clean for secrets. |
[2531.98 --> 2532.08] Yeah. |
[2532.18 --> 2537.32] You don't realize just how many service integrations you have until you go to rotate all your secrets. |
[2537.66 --> 2545.76] And then it's like, holy cow, Slack, campaign monitor, GitHub, Fastly, AWS, GitHub. |
[2546.40 --> 2546.84] Notion. |
[2547.40 --> 2547.84] Mastodon. |
[2548.02 --> 2549.26] Yeah, GitHub twice, by the way. |
[2549.26 --> 2551.56] You said GitHub twice because GitHub is used twice. |
[2551.84 --> 2554.46] So, you have API token and client secrets. |
[2555.06 --> 2556.10] So, yeah, we actually. |
[2556.20 --> 2557.28] Same thing with Slack. |
[2557.38 --> 2559.96] There's like two different Slack APIs that we use. |
[2560.18 --> 2564.84] One's for the invites, which is like this old legacy thing that was never an official API. |
[2565.48 --> 2566.74] How you actually generate an invite. |
[2566.90 --> 2570.54] And then everything else is like for LogBot, which is our Slack bot that does a few things. |
[2571.18 --> 2573.14] Yeah, there's just so many of them. |
[2573.26 --> 2576.16] And then it's like, it's just an arduous process. |
[2576.16 --> 2583.04] So, this is why my personal private key is years old at this point. |
[2583.56 --> 2584.32] Embarrassingly so. |
[2584.82 --> 2585.82] We have to rotate it again. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.