Welcome to American Issues Take One. I'm Tim Apachele, your host. And today's title for the show is Some Nations Support Putin, also MAGA GOP. In March, 2022, the United, the UN took a resolution vote on the Ukraine invasion, Putin's war. And out of the vote, 141 nations voted to deplore Putin's invasion of Ukraine. 35 nations abstained from the vote and four supported the Kremlin in its invasion. But we know there's a lot more countries that are either directly helping Putin and his invasion or indirectly. And we're gonna talk about those nations, but more importantly, there's physical ways of supporting a country that's purchasing oil or sending weapons. But there's the moral contribution, how people can help Russia in this effort. And that's the MAGA GOP, which we saw some inklings of here recently from House Speaker Kevin McCarthy and his proclamation that no longer will, there'd be blank checks written for Ukraine. We'll talk about that and more. I'd like to introduce my guests. Today we have our special, special guest, Chuck Crumpton. We have, of course, always my co-host, Jay Fidel.  Good morning, everyone. Morning, Tim. You know, Jay, in the intro, I just mentioned, there's ways that these countries are helping Vladimir Putin, specifically China with their purchases of oil. Iran recently has been identified, I believe, by the CIA as the ones that are supporting them with the deadly drones that's causing a lot of damage to Ukraine's infrastructure system, power plants, electric plants. And what are we seeing from these countries? What are the explicit things they're doing to help Putin and maybe some of the behind-the-scenes activities that these countries are doing to help Vladimir Putin in his invasion? Well, we know that they're supplying mercenaries through the Wagner group. We know that. That goes beyond the countries that you mentioned as part of the four that, you know, opposed aid to Ukraine or condemnation of Russia in the United Nations. But there may be other things too. There may be espionage. There may be sharing of intelligence. We really don't know. Suffice to say is a good guess to say that they're doing something else besides buying oil and gas. And then there's the moral thing. It's depressing to find that these countries are opposing the United States position, at least the current United States position. We can talk about that. And that they are supporting a psychopathic dictator. That's really troublesome. And the reason why, of course, is that Putin is influencing them. He's influencing countries in Africa, Latin America, and elsewhere in the world, either through economic pressure or intimidation or who knows what, leader by leader. But he's been undermining their moral suasion, their norms, and it's regrettable that the world does not universally, unanimously condemn him. You know, I mentioned Iran, giving their drone technology to, it's not really technology, they're pretty basic drones, but they're quite effective. Their Kamikaze drones and Vladimir Putin has taken advantage of that offer and is doing quite well with those drones. But how should we look at Belarus? Remember, they allowed Russian troops to stage in their country. There was a staging area before the invasion took place in February. They've allowed Russia to fire missiles from their sovereign soil. They've conscripted doctors to impress them into service to take care of the Russian wounded. That article is just coming out. They've allowed the refueling dump areas for Russia. And they've allowed Russian jets over their airspace. To what degree do we say Belarus is really a very close access power to Russia and should we be treating it as such? That's a delicate question. In fact, what's his name, Lujchenko? Yes, President Lujchenko. He's a puppet of Putin. He's been a puppet of Putin for a long time and he has allowed this sort of thing for a long time. Maybe we haven't focused sufficiently on it to reveal it spotlighted for the world. The last I saw on it though is that Putin could have his way with Lujchenko on anything but boots on the ground. And that's the standard here. Whatever Putin wants, Putin gets from Belarus except Lujchenko has said no to allow to use his military in the war. That's not a big deal in the sense that Belarus doesn't have a military. I think the total number of troops is something 40, 50,000. It's really small stuff. So Putin is really getting all he can from Lujchenko and Belarus. Let me ask you this. Is it time for the EU and the United States to consider sanctions against Belarus? I think anyone who cooperates with Putin and offers him this kind of assistance and no question about Iran, maybe other countries should have sanctions too. I mean, India is not our friend on this. They're buying oil and gas from Putin. They're doing other things to support Putin. They voted against Ukraine and the United Nations. That's really disgraceful. They're supposed to be a democracy but they're moving right. Modi is moving right. A lot of countries are moving right and their action in supporting Putin is kind of an expression of that. As for whether Belarus should be subject to sanctions, I think it's a great idea. I don't know why Biden doesn't do that. I don't know if Belarus is in the EU. The EU could take action against it. The US could take action against it. There should be, could be sanctions against it. They are doing everything they possibly can do to help Putin. Okay, thank you, Jay. Chuck, to you, by the way, thank you for coming on today, appreciate it. To you, even in our own country, we seem to have key GOP members, the Speaker of the House comes to mind, Kevin McCarthy, almost lending moral support in that which Putin has been waiting for and that is to try to fracture the unity in the European Union and certainly any support for Ukraine from the United States. And it came in the form of a very pronounced statement that there will be no more blank checks as it pertains to support for Ukraine. We also had Margaret Taylor Greene, not the spokesperson for the GOP, but certainly a key leader for the MAGA GOP. And she said she's sick and tired of billions of dollars being spent for Ukraine when that money could better be served at the southern border. We also have Katie Vance is basically making his statements, basically following the Trump lead on America first and his viewpoints of isolation. To what degree is the GOP, Chuck? I won't say aiding and abetting Putin, but certainly not making it easy for the Biden administration to have a unified front as we support Ukraine. Okay, well, in mediation, one of the country's great mediators, David Hoffman in Boston at Harvard, coined a phrase called reactive devaluation, which is fancy for, if the guy on the other side says it, I'm again it. So for the GOP, this is election season. Anything is a ground for attack against the Democrats. The only thing that they can attack concerning the Ukraine because the support is popular nationally is the money because the money relates to their primary election issue, which is inflation. Inflation generated during Trump's time by tax cuts that drove an incredibly increasing wedge between the upper elite wealth and the rest of the country's resources. Their pitch is basically, hey, Biden touched it last, it must be his fault. What is it who touches it last? That's the blame that goes to everyone, every president through points. And there's kind of, you asked a good question about Belarus and Iran and the contrast between those two situations relates to that same kind of reactive devaluation tar the other guy issue, which is for Iran, anything against the U.S. and its leadership is worth supporting, no matter what it is. And if that has impacts on the EU, so much the better. For Belarus, the situation is different. But Jay, I think characterized it really well. You've got a puppet leader who is hanging by a thread dependent completely on Putin for not being annexed, taken over or replaced. Yeah, Chuck, let me mention that Belarus is one of the poorest countries, if not the poorest country in Eastern Europe has no money. It is absolutely dependent on Putin. That's a great point because the answer to Tim's question is, what would you sanction in Belarus? Yeah, let's let the sanction, okay. They don't have oil and gas reserves, they won't have. I mean, they're a staging area, but so what? Yeah. Were you surprised, Chuck, when Senator Minority Leader McConnell basically came out very strongly in support and in opposition to Kevin McCarthy's statement, he said the following, the Biden administration and allies need to do more to supply tools for Ukraine and thwart the Russian aggression. And he made a special point to say that all support so far for Ukraine has been an unanimous by-supportive support of Ukraine. So he came out very boldly and didn't care about what, by embarrassing Kevin McCarthy or not. He basically drew a line in the sand saying the GOP will support Ukraine, at least in the Senate. Were you surprised that he came out that boldly? Not at all. McConnell was there before all these guys, Trump, Rubio Cruz, the rest of them, he'll be there after them. His base in Kentucky is virtually unshakable. And his strength is he can bring every Republican vote to the table and he can do that because he has balanced his access to the Republican donors, the reserves, the power of the contributions and the electoral support for them. He doesn't have to depend on Twitter and these guys. He provides the support that gets those guys the resources to be able to make the races close enough where they have a chance to win. McConnell knows exactly where his strengths are. He kind of reminds me of one of our late judges and former state senators, James Wakatsuki, who was known for his ability to not only marshal votes, but count votes. McConnell is an expert at that. He does it probably better than just about anybody. The ability of Nancy Pelosi to be able to do that as well as she has in the House, despite a divided democratic base and people like Manchin and Sena Ma and the progressive caucus and others, that's pretty amazing. I mean, you got to give her credit too, but McConnell is literally unmatched. Sam Irvin and those guys from the olden days, Bob Dole, nothing compared to McConnell's ability to bring every single Republican vote, even against things that have 60, 70% popular support. Yeah, I think Kevin McCarthy realized his power and strength just recently because he recanted his statement about the blank check and he said, I was taking out a context. So I think being taken to the woodshed by McConnell was sobering thought for Kevin McCarthy and he quickly has backtrack or moonwalked away from his blank check statement, which I think is very funny. Thank you, Chuck. You put it very well, Tim, because what McConnell has reminded McCarthy is, bro, you're not in context yet. We haven't won the midterms yet. You're not speaker of the House yet. So if you want to get there, show a little respect. Good point. You're laughing, Cynthia. Why? Because I think that the only thing McCarthy respects is power and money. So let's speak or not. Well, Cynthia, I want to get your thoughts on these recent overtures from the mega GOP. I won't say the GOP. I'll say the mega GOP, because they are following a script from Donald Trump. Donald Trump's praise for Putin is genius and savvy. His go-to-lone of America first isolationist position. Yeah, we have the mega GOP basically trying to say, support for Ukraine is an top priority. What do you think about that? Their position they're taking in, is it a losing strategy? Because most Americans do support Ukraine. I think it is a losing strategy. And to answer one of the things that Jay was talking about, Belarus has been a member of the EU since 2009. Just for a matter of fact. Okay, so I think that the House passed $40 billion for aid. This was just recently. So it wasn't just the Senate that was bipartisan. The House was bipartisan too.  Just those few GOP's. I don't think it's going to carry well just those few GOP's. And we got to remember in the beginning of this back in February, they were praising Putin. Remember when Trump came out and said, he's a genius. He's real savvy with what he's doing. And then all of the mega GOP, I'll call him that.  I know you do, but we'll keep it to MAGA. So the MAGA GOP has completely came out in support of Putin, that what he's doing is right. He's just getting his country back together as if the Soviet Union was something that was good and should be put back together. So they just don't have a realistic view of what's really happening in Europe.  And especially after everything that Biden has done to get NATO knitted back together and strong. I think if the House decides to try to undermine that, it's going to really hurt NATO, which we know the MAGA GOP led by Trump want to do. So it's sort of all going with that. And I think that we don't really hear about it on the news that the media is just treating the MAGA GOP as if they were rational, respectable people that should be treated that way. Instead of separating them out, it's just been recently. And it's only on MSNBC or NBC that I really hear that happening is to sort of separate out the MAGA GOP from the rest of the GOP. And I think until we do that, all hope is lost really, because those MAGA GOP that are in their races right now, trying to get elected and are looking like they might be, we've got to separate them out from normal people. So, and we've got to do it quickly because we've got two weeks until we vote. So, Tom was too late. All right. You are quite correct in what you state as the initial praise for Putin and his efforts in Ukraine from Donald Trump and his acolytes, the MAGA GOP, they switched though. They switched because why? Was it some consultant saying this is, you're going against the polls of most Republicans or was it some other reason they've switched? So that's a two-part question. Why did they switch from praising Putin to supporting Ukraine and it's the many billions of dollars we've sent them? And secondly is how does that change if the House of Representatives swings back to the Republicans? Well, I think the problem with the MAGA GOP is that they will say whatever they need to say to get the most reaction, good reaction from people, to buy their votes, to buy their support. They will lie. We know it is their strong suit, is how to lie and when to lie. So first, they're talking about Putin and how they support him. And then suddenly it's not the popular thing, like you suggest. So they drew back. They didn't really stop. I mean, they didn't really start to support Ukraine. They just stopped being vocal about supporting Putin. I think they just got quiet. I don't think they turned around and said, oh, well, now we think Ukraine should get everything.  Okay, do they spark up if they win the House? Oh, they're gonna come out full bore with it. You think so.  We should be spending it on ours except for the fact that some of these MAGA GOP that are saying these things are the ones that got PPP loans and then got them forgiven to the tune of a million dollars. Even Marjorie Taylor Greene had hundreds of thousands of PPE dollars that were forgiven. So all of this, we need to be fiscal. It's nonsense. It's a lot. Let me lay over Chek's comments about Mitch McConnell the strength and power he brings to the table. Mitch McConnell's not gonna swing that way. I doubt he will. If the House is taken by the GOP and you according to your prediction, they'll spark up more about waning support for Ukraine. What does Mitch McConnell do about it? And will he be successful to put them back in their box? Well, I think that Mitch McConnell realizes what very few people are talking about. And that is that Ukraine has more lithium in its ground than any other country in the world. And right now with everything turning to lithium batteries, boy, whoever has control and power and voice in Ukraine is gonna be in a better position. And I think that Mitch McConnell can see those kind of, he sees the long game. He has those, he doesn't have that short-sighted view that I think people like Kevin McCarthy and Margie Taylor-Greenham. Okay, great. Thank you. Hey, Jay, just before the show, we were talking about House Representative, Jaya Paul. She is the chair of the Progressive Party of the Democrats. And this letter that went to the Biden administration about strongly encouraging to negotiate a peace settlement with Putin. We talked about that. And to what degree does that help Putin? To what degree is that a moral support that the Democrat current administration can be fractured? Does it give Putin a reason to try to wait things out? I think it's only part of a huge piece well of change. You talked about the hypocrisy of the Republicans who supported Ukraine earlier this year, changing their minds, at least some of them. But at the end of the day, we're in the middle of a sea change on that issue. She reflects the sea change on the progressive side. And the letter she wrote and then withdrew was wrong and ill-advised. And I'm personally disappointed in her for writing a letter and a progressive group now as no credibility. They held up the infrastructure bill for months. And now this, anybody with half a brain would have known that this is very damaging to the administration, damaging to Ukraine. Because it reflects a fracture, as you said, as you suggested. But it's only part of the sea swell. There are other things happening here. Maloney in Italy is moving to the right. She's not gonna support Ukraine. If Le Pen wins the next election in France, she's not gonna support Ukraine. We have a kind of chaos going on in the UK, not clear what they're gonna do. That's really regrettable. Not only on the basis of their government policy, but on the basis of their economy in general. They may not be able to help. There was an article in the New York Times yesterday about Olaf Scholz in Germany and how he is holding back on money and military equipment to Ukraine. And being attacked for it, but the fact is he's holding back. So what we have is a fracture happening globally. It goes beyond what you and I were talking about a minute ago in terms of the countries that are not supporting Ukraine. But now countries that used to support Ukraine are not following through in their promises. And indeed, the United States is not really following through in its promises, both in terms of money and in terms of military equipment. The drones are having their way. So we have a sea change that's happening right now. And that's a static statement of it. But if you look forward to the elections in two weeks, it's more than likely that the Republicans will take the house. More than likely that they will be subject vulnerable to a Trump's position on things. And Trump would like nothing more, as Chuck suggested, than to attack Biden in every conceivable way. That's his, you wanna know what his policy is? It's to attack Biden. That's it. Then everybody who follows him will attack Biden. And if the house turns Republican, whether it's a Mac or Republican or halfway, they will attack Biden. This will be a wonderful part of attack because as the economy goes further to a recession, as we struggle with inflation, this is a part of the whole process. Just take that, swing it around and attack Biden for spending money on Ukraine. It was another article in The Times yesterday or today, I guess, about why people are in Trump's base. And it's really interesting. It's almost oversimplisted to say they wanna win. They wanna win the election. They want power and they'll do anything to get power. And the reason they follow Trump, they reason they follow the big lie and the big lie coming in two weeks, that big lie, the one that's gonna result in secretaries of state doing strange things and of course, litigation for years about who won. That is just a way of retaining power. Chaos is a way of retaining power. And if you wanna win, you follow Trump. And if Trump says the big lie, you accept that. And so we have a real problem in MAGA GOP, but in GOP in general. So the House controls the funds, remember? The House is the money part of the Congress and they are very critical in terms of whether it can keep on funding Ukraine. The Senate is not certain. You know, Fetterman is not certain. God knows whether the polls we talked about this before are true, there was another article, I think in the Washington Post, questioning whether we should listen to these polls. Who knows what's gonna happen in the Senate? Who knows how powerful the GOP and the MAGA GOP and Trump is in terms of the electorate and the base in this country. I am not optimistic. We can lose both chambers of Congress. Very problematic and one of the things that's clear is that what is emerging here is an isolationist approach and isolationist nationalistic feeling in the country and among them and them in Congress, determining policy and making votes against Ukraine. So if I were Zolensky, I'd be very concerned that in Europe and other places in the world and in the US people, countries are moving to the right. Not just their leaders, people are allowing them to do this. There is a new time in the air, including the US. And I don't think he can count on having continued support.  Jampow's move showed a fissure in the will to support Ukraine, but it's also a cease well in many directions. And I think what's gonna happen is we wind up being completely hypocritical about it, not supporting Ukraine, including the man on the street who was much more interested in a gallon of gas, in inflation, in the grocery store that he could give a rip about the liberal world order. Okay, thank you, Jay. Chuck, what's your take on the letter from Representative Jopiah Paul to the Biden administration and certainly the 30 signatures she got on that letter. What's your take on that letter and was it damaging? Did it give Putin more hope that he could wait things out? Well, I think the effect is much less than going back to McConnell and his deeper and longer term understanding of the reasons for the strategy, the billions and billions of dollars that Congress, both House and Senate have approved for the Ukraine, those are not going into Ukrainian bank accounts. They're going into defense contractors and intelligence, US bank accounts for a, in weaponry, in defense and intelligence, which are critical to Ukraine's successes militarily and politically. McCarthy may think that in the short term, casting doubt about US support for Ukraine may erode the unity and the strength of NATO that has been a really big foreign policy advantage for the Biden administration. But McConnell understands, hey, that money is going to the people who are the hugest sector of our donor base. And with Afghanistan reduced, and most of the other places where we're putting a lot of money, Iran, Syria and others reduce, this is a place to funnel huge amounts of the defense appropriations, which continue to grow, even if US participation in foreign wars theoretically superficially decreases. So follow the money. Good point, Chuck. Excellent point. I don't think that's going to have any impact on that at all. The love of money is the root of all evil. That's a good point. All right, we've run out of time. I'm going to go around the table for last thoughts. Cynthia, I will start with you. Your last thoughts about this topic. I think that Chuck is exactly right. It's all about money. It's all about greed, power and greed. And his point about the fact that the money we're giving them isn't cash money. We're giving them weapons and weapon machinery. And those are things that are made here in America so that to actually going into our coffers, like you said, Chuck, I think it's an excellent point. Really, because I was going to say that same thing. So I was really, except for I'm like, okay, now what do I say? Because he just said it. Do you have a quote for us? Of course I do. Okay, let's hear it. And this is a quote from one of the, from Representative Sarah Jacobs, the Democrat from California, who signed on to that letter, says, timing and diplomacy is everything. Such an important point. I signed this letter on June 30th, but a lot has changed since then. I wouldn't sign it today. And I think there's a lot of them that are saying the exact same thing. And yeah, maybe in the beginning in February, it was possible to try to get some sort of diplomatic action going. And we did. We were sending diplomats over there. Ukraine was sending their diplomats over there. And it wasn't going to work. And they saw that it was just a waste of time. And all it was doing was giving Putin more time to undermine and do what he wanted to do. And so I think the fact that this letter was released right now is, I think was maybe even done out of spite and on purpose to cause trouble by someone. So maybe it's possible that it was someone on her staff, but, and maybe it's someone on her staff that wants to undermine things because otherwise there's no other reason for it. Okay. Okay. Thank you, Cynthia, very much. Jay, to you. Well, I think we have to keep our eye on the election here. And the election's coming in two weeks. And it will have profound effect on democracy, as everyone says, and on the country and on the Congress. And if we have just the house turning Republican, we have much greater control by Trump on all of these issues. And he's going to try to do damaging things for sure. I think that Democrats are not together and that's demonstrated by the Jay Powell letter. And I think that the Senate is still at risk in terms of turning Maga Republican. And if the Senate turns, you know, your friend McCarroll may not be, you know, in office. So I'm not optimistic about this. I'm not optimistic for the country, the Congress, the people, we've discussed all these things before. And I'm not optimistic for Ukraine. I think we have a kind of, you know, the fickle finger of fate is moving. The news cycle is moving. There's a kind of fatigue, a sea change, as I mentioned. So watch out how, what is happening today, what looks like, you know, the reality today, could change dramatically in two weeks' time. All right, Jay, thank you very much. As always, Chuck, you get the last word for today. Look at the money, right? Billions and billions, theoretically further Ukraine, but as Cynthia points out, into American defense and intelligence contractors' pockets, the primary portion of the Maga GOP donor base followed almost simultaneously by millions and millions coming out of that Maga GOP donor base into candidates in these 2022 midterms, many or most of whom are far right Maga GOP candidates, selection deniers and others. The likelihood that they're going to cut off that funding before the 2024 elections seems small. All right, you know, you said something that just caught my eye because if I recall, some money from the Democratic Party went to fund these wing nuts. And that's unforgivable, but that's another show and another day. I like to think- We're going to show tomorrow where we're going to examine Trump's relationship with Putin. And if you follow that relationship, I know you have to follow the money, if you follow that relationship, you will see that Trump and his base want Putin to win. They want to support Putin and Putin wants Trump to win. That unholy alliance has a lot to do with this, money or no. Okay, good point, Jay. All right, Chuck, did you have anything else to add? No, I just think you're spot on because Trump sees connections as power elite corrupt connections. Correct. Others have a different worldview than that. Alrighty. I want to thank my guest, my special guest, Chuck Crumpton for today. Thank you, Chuck, for appearing on the show. My co-host, Jay Fiedel and certainly Cynthia, Lisa and Claire. Thank you one and all. Won't you join us next week for American Issues Take One? I'm Tim Appichell, your host. We'll see you then. Aloha. Thank you so much for watching Think Tech Hawaii. If you like what we do, please like us and click the subscribe button on YouTube and the follow button on Vimeo. You can also follow us on Facebook, Instagram, Twitter and LinkedIn and donate to us at thinktechhawaii.com. Mahalo.


So this is a quick demonstration of the distinction of the posterior compartment of the thigh, the so-called hamstring compartment. This is the lateral intermuscular septum, which is separating this compartment from the vastus lateralis. And these muscles that we see in front of us, these are the hamstring muscles. In this particular cadaver, these muscles were necrotic and they were already ruptured, so I had to tie them with a tape. This bone that we see here, this is the ischial tuberosity. And a common feature of all these hamstrings is that they take origin from the ischial tuberosity. We will see the insertions as we go along. Let's pick up this muscle on the lateral aspect. This is the long head of the biceps femoris. The next muscle that we see here, this one, this is the semi-tendinosis. And the third muscle that we see here, this is the semi-membrinosis. So the semi-tendinosis is superficial to the semi-membrinosis and they are like this. This is called tendinosis because it is like a tendon. And this is called semi-membrinosis because it is fleshy. So these are the three classical hamstring muscles and their common action is extension of the hip joint by virtue of origin to the ischial tuberosity. The semi-tendinosis is inserted in the pesanserinas along with the gracilis and the sartorius. So I have lifted up these three muscles. So sartorius, gracilis and semi-tendinosis. And the three common insertions is called the pesanserinas which is on the upper middle side of the tibia. This is my hand picking up the three insertions of the sartorius, gracilis and semi-tendinosis from another dissection. The goose boot appearance of the pesanserinas is clearly visible here. And between the insertions of the pesanserinas and the tibia there is a bursa and we can see this bursa here. This is the ancerine, remnant of the ancerine bursa. So this is about the insertion of this semi-tendinosis. Now let us take the insertion of the semi-membrinosis. The semi-membrinosis gets inserted on the upper middle aspect of the tibia and it gives expansion to the posterior capsule of the knee joint. It also gives the archivate and the oblique propitial ligament and it also reinforces the propitius fascia part of which can be seen here. This is the semi-membrinosis. There is a bursa between the semi-membrinosis and the gastrocnemius medial head and this is that bursa. We can see that bursa here. This is the semi-membrinosis bursa. Now let us take a few exceptions to the rule. Hamstrings are extensors of the hip joint and they are flexors of the knee. Though they cannot do both of them to the maximum extent together. But there are exceptions. Let us take the exceptions one by one. This muscle that I have picked up here. This is the short head of the biceps femoris and we can see it is not taking origin from the ischial tuberosity. It is taking origin from the linear asper of the femur. Therefore, this muscle though it unites with the rest of the biceps to form the biceps femoris tendon which gets inserted onto the head of the fibula. But this component of the muscle is incapable of extending the hip joint. So this is one exception. Let us take the next exception and for that I will reflect all these muscles and we see this muscle here. This is the hamstring component of the adductor magnus and we can see that it is also taking origin from the ischial tuberosity. The posterior component of the adductor magnus, anterior component is the adductor component. This though it is taking origin from the ischial tuberosity, its insertion is by means of this tendon that we see here to the adductor tubercle. So therefore, the hamstring component of the adductor magnus can extend the hip joint but it cannot flex the knee joint because it is a one joint muscle. In contrast to the other hamstrings which are two joint muscles, this does not cross the knee joint therefore it cannot cross the knee joint. So these are the two exceptions. Coming to the nerve supply, all the hamstring muscles are supplied by the tibial division of the sciatic nerve which I shall show you just now except the short end of the biceps which is supplied by the common fibula. So these are a few quick words about the hamstring muscles. Now let us take a look at the nerve supply. This nerve that I picked up here this is the sciatic nerve, the largest nerve in the human body and we can see that the sciatic nerve emerges from the gluteal region between the ischial tuberosity and the greater trochanter. It runs on the deep muscles of the gluteal region and it enters the thigh. It runs between the two heads of the biceps femoris, the long head and the short head and then it runs between the hamstrings and the hamstring component of the dr. Magnus. Ideally somewhere in the junction of the upper two-thirds and the lower one-third of the thigh it is supposed to divide into a tibial division and a common fibula. But in this case we see that it is dividing a little lower down in the paupitial fossa into the tibial division and common fibula which I shall describe when I come to the paupitial fossa. So this is about the sciatic nerve. We know that normally whenever there is a big nerve there has to be arteries and veins accompanying it. But in this case we do not see any artery accompanying the sciatic nerve. So how do these muscles receive their nourishment? For that I will draw your attention to what is known as the perforating arteries of the profunda femoris. And we know that the perforating arteries there are four of them. They perforate through the insertion of the adductor magnus at the linea aspera and they go from medial to latrine and they come to the posterior spate. So let us take a look at the four perforators. This is the first perforator which I have picked up here. This is the insertion of the adductor magnus to the linea aspera and we can see this is the first perforator. This is perforator number one and we know that the first perforator participates in the cruciate anastomosis and this is the branch which goes to the cruciate anastomosis. The rest of the perforator it supplies the hand string muscles. This is the second perforator. This is perforating again through the insertion of the adductor magnus at the linea aspera and we can see it is supplying the hand string muscles. The third perforator is this one here. This is the third perforator and I can turn it here to show you the third perforator. This is the third perforator and I have lifted it up here with my instrument. This is perforating through the insertion of the adductor magnus and finally this is the fourth perforator. This is the fourth perforator. It is also perforating through the adductor. This is the terminal perforator and this is the termination of the profunda femoris. These four perforators with their accompanying veins, these are the ones which supply all the muscles of the posterior compartment, all the hand string muscles. That brings me to the next important point. We see this is femoral vein which has become the perforatial vein. This is the femoral artery which has become the perforatial artery. They are emerging through an opening, a hiatus and my finger has gone through the hiatus. This hiatus is referred to as the adductor hiatus. This is an opening between the hamstring component of the adductor magnus and the adductor component of the adductor magnus. This opening in the insertion of the adductor magnus is called the adductor hiatus and this is the place where the femoral artery has become the perforatial artery. This is a location where the femoral artery can get occluded, compressed or entrapped and this is one of the sides of femoral artery entrapment. That brings me to the final point that is about an important clinical correlation. As I told you the common action of hamstring is extension of the hip and flexion of the knee. In Olympic hurdle jumpers when they are doing extreme sports they have to flex the hip to its maximum extent and extend the knee to its maximum extent and in both these situations there is tremendous traction exerted onto the hamstring muscle especially at its origin. In such situation it can rupture here and that is known as hamstring tendon rupture or if the person is an adolescent and the ischial tuberosity has not fused it can evulse the ischial tuberosity and that is known as abortion fracture. This is the next story of the pelvis of an adolescent to show abortion fracture of the epithesis of the ischial tuberosity. So this is one of the important clinical correlations pertaining to the hamstring muscles. So that's all now for the hamstring group of muscles. If you have any questions or comments please put them in the comment section below. Dr. Sanjay Sanyas, Sanyam. Thank you.


Deaf woman falls 600 feet down a mountain, then suddenly realizes she's not alone. Amelia Milling knew that hiking through snow alone was risky business especially for someone with a disability. Even though there's nothing quite as peaceful as exploring the snow-covered wilderness, an accident can bring it all crumbling down. During a solo mountain hike in Alaska, Amelia slipped and took a nasty 600-foot fall. When she realized the state of her injuries, she looked up to find she was not alone. Amelia was a student at Rochester Institute of Technology. Meeting a break from her studies, she decided to take a three-day solo hike in the beautiful Alaskan Mountains. She already knew it wouldn't be an easy feat, especially for a young deaf woman on her own, but she was up for the challenge. The 2018 hike started perfectly. The air was crisp, the sky was blue, and Amelia was full of energy on that Alaskan summer day. Things were so perfect, in fact, that Amelia didn't notice a patch of ice at the trail's end. Losing her balance, she slipped and fell 600 feet down the side of the trail nearly the length of two football fields. Amelia's body was battered and bruised from slamming into rocks and trees on her way down. She had no way of knowing if anyone nearby heard her cries of panic. Likely, she was on her own. Before she could work her way back to civilization, Amelia had to figure out just how bad her situation was. When she tried to stand, her legs shook, making it difficult to stay up. She badly needed help. She grabbed her satellite messenger. Amelia tried and tried to reach someone for assistance, but it appeared her messenger had also been pummeled during the fall. Just as her darkest fears began to creep in, Amelia caught sight of a figure moving through the white snow. It was headed in her direction. Amelia was frozen in fear. After all, these woods were home to all sorts of dangerous creatures out on the hunt. Perhaps this was a wolf who thought she was an injured animal. And Amelia was an injured animal. She braced herself as the creature leapt toward her. As the animal's weight came down on her, Amelia was surprised to feel it accompanied by repeated, rough licking. It was a beautiful white husky. Amelia couldn't believe her eyes. The dog had a collar, meaning it wasn't a stray. The second she read the dog's name, Amelia knew she was her guardian angel. The dog's name was Nanook, which is an Alaskan Inuit name meaning polar bear. Nanook barked when she heard her name, rekindling Amelia's withering hope. Amelia used all her strength to get on her feet and start moving. Nanook ran ahead, turning every few feet. They were in it together now. Unfortunately, Amelia was still struggling to move. But that didn't bother Nanook, who stayed patient as they shuffled through the untouched snow. Amelia prayed that Nanook knew the way, but she had her doubts when they came across a dangerous obstacle. Nanook led them to a frozen lake. Amelia tried to persuade Nanook to go a different direction, but the husky insisted they cut across the frozen tundra. Amelia, noting Nanook's confidence, decided to follow. She moved along, slowly and carefully. After making it a few yards out, Amelia heard a sudden crack. First one crack. Then another. Within moments, the ice below Amelia was crumbling. Just as she went to move, the ice below her gave out, dropping Amelia into the freezing cold water. She screamed out for help, and Nanook came running. With no hesitation, Nanook jumped right in after Amelia. She used her teeth to pull Amelia up above the water, and then doggy paddle to the ice's edge. To survive without freezing, Amelia would have to crawl out fast. But she could already feel her body going into shock. Nanook pulled herself out of the water and began tugging on Amelia's clothes. With Nanook's help, Amelia swung her leg up and scooted herself on top of the ice. Once again, Nanook had saved her life. But now her body temperature was dangerously low, and walking seemed impossible. So she could warm back up, Amelia hurried into her sleeping bag. To her delight, Nanook crawled right inside with her. The heroic husky licked and licked Amelia's face, unaware that her body's warmth was saving Amelia from freezing to death. After some time, Amelia decided to try the satellite messenger once more. The messenger still wasn't working, so Amelia hit the side of it again and again. Finally, the screen flickered on. Amelia quickly entered the SOS signal and sent it out. Then, it was a waiting game. Thankfully, she had Nanook to keep her company. But how long would they have to stay put? Hours passed, and the colors of the sky changed above them. Amelia was beginning to worry that her signal had failed. Should she and Nanook start moving again? As fearful thoughts filled her mind, Amelia began to drift asleep. Suddenly, the ground's vibrations shook her awake. Nanook felt it too. As a deaf woman, Amelia immediately recognized the significance of the ground's vibrations. Nanook began to bark as they grew more intense. Soon, dirt was rising into the air. While shielding her eyes, Amelia tried to make out the source of the vibrations. High above Amelia and Nanook was a rescue helicopter. Her SOS signal had been received after all. Amelia waved her arms desperately, hoping the pilots wouldn't miss her. This could be her last chance. Amelia nearly burst into tears as the helicopter descended. They finally were saved. The rescue team took them into the sky and Amelia was rushed to the hospital. It didn't take long to see that her wounds would heal fine. Now, Amelia needed to know, where did Nanook come from? State troopers contacted the number on Nanook's collar. Within an hour, her owner, Scott Swift, arrived at the hospital. He'd been worrying about Nanook's whereabouts, but wasn't surprised when he heard what she'd been up to. Apparently, this wasn't her first time saving Hiker's lives. Nanook had previously saved three other Hikers who'd lost their way on the icy trail. It was astounding. Scott was beginning to see a pattern, so he decided to start a Facebook page to see if anyone else had been aided by the heroic Husky. He was shocked by the response. Many people responded to share their stories of meeting Nanook on the trail. They were overjoyed to give thanks to the incredible pup, but none more than Amelia. Of course, she hadn't yet heard of the Orylus of family whose four-year-old son nearly lost his life at the mercy of a far less friendly canine. Although the Orylus called New Hampshire their home, they spent far more time outside the house. Ian and Allison passed on their passion for the great outdoors to their kids before they could even walk, but the parents never expected to place their children in danger.


Welcome to the GitLab 13.4 release showcase. We'll show you some of the newest features released in 13.4. Hello, my name is William. I'm a technical marketing manager. Today, I will cover a new feature for inline code test coverage right in the Merge Request View. So, what is it? It is a visual representation of code test coverage right in the Merge Request located in the changes view. Orange when no test coverage was found and green otherwise. And why is this important? By having this view available at the moment of reviewing code in a Merge Request, it is easier to determine if the code has been tested, leading this way to a faster and more efficient reviews that ultimately speed up merge and deployments. Follow these links to learn more. And if you want to replicate my demo, under the demo repo, you can find the project. Let's jump to the demo. So, here we are in a project. We can see that Sasha, the developer, has some issues assigned. She selects the first one and creates a merge request from where she will make some changes to the code. Once she's done with the changes using the Web IDE, she will assign this merge request to William for further review. Now, we can see that William gets the merge request assigned, opens it and under the changes view in the merge request, he can find out if the code has been covered by unit test. This information comes from a code coverage tool used to measure the effectiveness of tests. It can show which parts of your code are being exercised by tests and which are not. This information is available in the merge request, making it easier for the reviewer to approve or not the MR and overall, speed up the code quality and deployment process. And how do I do that? Very easy. By taking advantage of the power of GitLab CI. In the GitLab CI YAML file, add the necessary scripts to execute your test coverage tool and make sure to save the report in XML format as a report artifact. Hi, everyone. My name is Itzy Ganbaru, technical marketing manager, and today I will talk about parent child pipeline and what's new in 13.4. Parent child pipeline is a way to split the long and complex pipeline to small modules. Everything runs in the same project, but instead of running one big pipeline and one CI configuration files, we can split it to small pipelines, smaller folders, and each folder has its own configuration file.  When it runs, it runs like a normal pipeline. So what's new in 13.4? Child pipelines now can trigger their own child pipeline. And this is useful for cases that where also the child pipeline become complex, now GitLab allows another level of nested pipeline. And currently supports nested child pipelines with depth of two real discussions to increase it to five, but this is currently can support only two. So why does it matters? As the pipeline become more complex, new challenges comes with the pipeline. First, the overall distribution time become longer, and when we speak about DevOps and CI CD, we try always to optimize the pipeline time. So our child pipeline breaks the normal stages and allows to reduce the overall pipeline execution time. The second thing is that it simplifies the configuration. Instead of having the one complex long file CI CD other file, of course, now we can break it to small models, which can be easy to manage. And maybe even different teams can manage their module and not the one team need to manage the entire pipeline. Sometimes we use the imports include, when we include the some templates, which is a great capability, but sometimes also it leads to complexity. Also it potentials for namespace collisions where jobs are unintentionally duplicated. So this solved the problems that we have been with the import includes. Instead of include, you can just trigger child pipelines. Here is another advantage is the ability in on runtime to determine if you want to start or not start a sub pipeline and the ability to dynamically define that and create dynamic child pipeline is very strong for some customers. How it works. Very simple. In the repository, you will need for each child pipeline to create a sub folder. In the sub folder, you will add a .github-ci yaml file for each child pipeline. You need its own CI yaml file. And in the parent, the yaml file to trigger the child pipeline, you will need the trigger job with this keyword trigger. And include the full path of the child configuration file. In this case, Android is the name of the directory. And if now what's new in 2004 is that the child can trigger another child is the same, but you will need to add the full path. Android, Google TV is another directory that I created. And this is how it works. You can also pass variables from the parent to the child pipeline. And a little more, we have my demo project documentation and we have, there is a blog for that. So short demo. So I created the spatial project for parent child pipeline. And so this is the parent. It has two childs and which are two directories that I created, 1200 and one for iOS. This is the main yaml file. And I have two trigger jobs. For the iOS and for the Android. And this is the keyword that I created. And also here keyword. And this is how I pass environment variable for the child pipeline. And let's go to visit the child. So this is my child. And it says it's online yaml. And this child also has three children. And again, here we have a trigger job. That's called to its children, to its child. If I will open the child again, it will have its own configuration with two jobs. The last part of this demo, to see the pipeline visualization and also here there is some improvement in Territor.4 about how you recognize the relationship between child and parent. So two trigger jobs that triggers child pipelines. And this is new. This arrow if you click here, it will open the child pipeline. And if you want to know what with the father, this is the new thing that they highlighted the father. Same here. You can click here to see this child. And this child, you can click here and see. And another child. And I can see the full path to the grandfather. Who is the grandfather for this child? This is his father. And this is his grandfather. So this is a parent child pipeline. It's important for customers because it's useful. It decreases overall exhibition time and decreases complexity. So go to know that it exists. Play with it. Thank you for watching. Bye-bye. Hello. My name is Cesar Cvedra. I'm a technical marketing manager at GitLab. In this segment, I'm going to be going over a new feature introduced in GitLab 13.4 called GitLab Kubernetes Agent. What is the GitLab Kubernetes Agent? It is a new way to deploy Kubernetes, two Kubernetes clusters. This is a brand new addition to our product. The agent itself runs inside of your Kubernetes cluster and it orchestrates the deployments by pooling new changes from GitLab rather than GitLab pushing updates to the cluster. This is also known as the pool-based CICD within GitOps. Why does it matter? So for customers, it matters because many organizations, they cannot open their Kubernetes clusters to the Internet because of corporate security compliance or maybe even government security regulations. This new capability will allow them to comply with both types of security regulations. And in short, no matter what method of GitOps customers using, GitLab has you covered, whether it's the pool-based approach to CICD which is this one here or the push-based approach to CICD which is your more conventional way of doing GitOps, which we already support that. So why does it matter to GitLab? So this new capability allows us to be on par with other competitors in the market that already offer pool-based CICD within their GitOps solutions. So now, in fact, many competitors actually only offer pool-based CICD. In our case, we're able to offer pool-based and push-based CICD within GitOps. And those two are actually complementary. It's not either or. You can use one of them only or both together combined. Here are some resources about this new capability. There's a link here to the documentation. There's another link to the issue itself. Soon as this video is public, I will update this presentation to provide the link right there on the left side of the first bullet. And then I also have a much longer video that is an end-to-end demo on how to install GitLab and install the agent on the server side and the cluster side in a demo and how the whole thing works. And things to follow, I'm providing here a link to our revision page for this capability. This is the first release. It's the first MVC that we put out for the Kubernetes agent. And right now it has a configuration-driven setup. And but in the future, we plan to add a lot more features like, for example, integration with the deploy boards and GitLab managed apps, as well as a UI to configure and set up the agent on the cluster. All right, so now let's move on to the demo. I have my own instance of GitLab up on running on GKE, which includes the CAS, the Kubernetes agent server. I have also installed the agent on the cluster. Here you see two projects in the GitLab account. The first one is Kubernetes agent, which contains the configuration of the agent itself, which includes the information about what project will be observed by the agent for changes. And now we're going to go to the GitOps project. This is the project that is being observed for changes. And we're going to go ahead and edit it. And we're going to kind of pay something from the documentation. It's just a manifest file that contains an Nginx deployment. It's going to be deployed under the same namespace of GitLab agent. And that's Nginx right there. And there are two replicas. So once we save this and it's committed to the mainline, the agent will detect that update. And then it'll communicate this to the other server side. It's going to communicate this to the agent. The agent is actually polling. And as soon as it detects the configuration change, it will update the cluster. And as you can see here, the agent has already deployed. The two instances of Nginx. And now, so that you can see how modifications can be immediately detected by the agent, we're going to increase the replicas to three. The agent is going to detect this change. And it's going to go ahead and act upon it and instantiate another pod with a third Nginx, which is right there. Now we have three. So this is a quick demo of the GitLab Kubernetes agent, which allows organizations to use a pool-based CI CD approach to GitOps and without having to expose their Kubernetes clusters to the internet. Hi, my name is Cesar Saavedra. I'm a technical marketing manager at GitLab. In this segment, I want to cover capability introduced in 13.4, track environments at scale with the environments dashboard. Since GitLab 12.5, you can only see seven environments across three projects with the environment dashboard. In 13.4, we introduced an improvement to the dashboard by paginating it to help you support and manage your environments at scale. You can now see more environments across many projects. In fact, you can add up to 150 projects for GitLab to display on this dashboard. Why does it matter? For customers on prospects, usually customers have hundreds of deployments running in their different environments. Besides production, they could have QA, pre-production, integration testing. With this new capability, they are no longer limited to seven deployments across three projects. They can now support and manage many deployments for multiple projects from a single dashboard at scale. This new capability can help you detect, identify, and troubleshoot problems faster. Why does it matter? To us, GitLab allows us to... I mean, the introduction of this new improvement allows us to better compete in requests for information, bids, requests for proposals, as well as proof of concept projects. Here are some resources to read up and learn more about this new improvement. There's documentation there, also the issue for this improvement. And on the right side, you see the link to the city direction page, which includes the area of the environment dashboard. And these are one of the things you should follow. Okay, so now let's move on to the demo. All right, so the way you access the environment's dashboard is by selecting the more menu. And that's how you get to the environment dashboard, and then you click on add project. And let's just search for projects that have the word spring in them. I know projects like that. So there's one, spring NBC JPA, and that has actually two running environments. And let's add some more projects. Let's look for spring again. And find another project that we can add to the dashboard. I think this one is a good one. There you go. That's two more environments. And let's add more projects. Again, let's look for the projects whose names have spring, the word spring. And let's scroll down and find more. There you go. That has only one environment. So let's continue adding more projects. So this time, let's look for projects that have the name Python in their names. So this new project has two environments, and actually they're failed. You can easily see that they are failed environments. And let's add one more with the name Python in it. And there's going to add two more. As you can see here, you have a total of nine environments. You can add up to 150 projects with this new capability. And as you can see, it allows you to see all the environments and on one single dashboard that can help you not just identify and detect problems, but also to troubleshoot them faster. This concludes this demo. Thank you very much. Hey, my name is Fernando, and I'm a technical marketing manager here at GitLab. Today I'm going to show you some of the new features and release 13.4. Well, let me go and share my screen. So the first feature I want to share with y'all is the grant user's deployment permission without code access. So what this does is you can give non-code contributors permission to approve merge requests for deployment and deploy code to what is called a protected environment. So what you can do here is you can give different people access, different groups access, and different roles access to be able to deploy onto protected environments. So one example would be reporters. You can allow them to approve MRs and as well as deploy to protect their environments. And you may want this because they may be some type of testers or some type of customers that want to interact with the product and you want them to be able to deploy the new code change to one environment that they belong to. But you don't want them to be able to access the code, but you want them to check out the new feature and test out the new feature. So there what you would do is you would allow them to deploy to their environment. Developer, same thing. They should be allowed to develop push merge into protected branches, but not into production. So that's like having a dev environment. And within the dev environment, you're giving developers deployment access, but they won't have deployment access to production because that'll be left for maintainers. And then managers and operators will follow the same flow as reporters where you want them to be able to deploy to certain environments, test certain features, but you don't want them to go ahead and mess with the project. And why is this important? So for customers, it allows better separation of duties. And it also gives code access to team members that may need to do emergency approvals and deployments. So maybe the development environment or the staging environment is broken and developers can't do anything and everyone's on vacation. Or different things like that, then approvals can be done by these members and they can also deploy. And you can also set managers probably to deploy to production if needed. So that way they have access for that deployment and they would do it in at a time of emergency. So it really enhances our situations like that, enhances testing and just allows more functionality and gives deployment access to those who really need it. And for us, it enhances our CI permission capabilities. So it just enhances our portfolio of capabilities we have within permissions. Some resources and now let me just show you how it works. So it's pretty easy to set up in the project settings.  You select protected environments and select an environment. So I'm going to say staging. And I'm going to allow all developers and maintainers to be allowed to deploy the staging and that's it. That's all I have to do. And that'll be a protected environment that developers and maintainers are allowed to deploy in. And this can even be changed to individual members or different groups which are part of this project. And that's pretty simple and that goes. And now let's move on to the next feature. So the next feature is a security center. This will be a quick one. So what we have done here at GitLab is we've made the Instant Security Dashboard more of a security center. So what we've done is we've kind of moved everything around and made everything a lot cleaner and a lot more organized. And it provides a better user experience. So as you can see, the biggest change is the menu structure. So rather than everything being on a single page, everything has been separated into little sub pages. And it just adds all the security related functionality to one page where a user can easily go through. And why does this matter? Well, it provides a better user experience for our customers. Makes it easier for them to navigate through the security context and assess the security posture of projects and groups of projects in more of a natural way without having to jump into different menus and different systems and find everything they have everything open one place. So it just enhances their experience. And for us, one reason why this is beneficial for us is it makes future enhancements a lot easier. So developers within GitLab can make it a lot easier to develop new features and new things within the security space. And all the security functionality can be added to one place so that way there's no confusion on where it is. Here's some documentation. And now let's jump into a quick demo. And this is how it looks. So you can see that there's a security tab. And from here, you can see the projects that are here. They're given a different security status, A through F, depending on the severity of the vulnerabilities found. There is a vulnerability over time showing how many vulnerabilities have been introduced and at what time they were introduced. And from there, you can see that you can easily access the vulnerability report that will have the different vulnerabilities within every space and can be sorted by status, severity, standard and project. And then you can also see that the settings are available as well. So you can keep adding different projects to build your whole instance level security dashboard. And yeah. And now to move on to the final feature, which is the most exciting one for me, is using Hashtag for both secrets and CI jobs. Now, what was added here in 13.4 is a new secret syntax for the GitLab CIMO, which is a secret syntax. And what this does is it allows GitLab to draw secrets and different variables that are stored as key value pairs in Vault and allows them to use them on your CI job. So a few things to consider about this. Vault is required. There needs to be secrets in Vault and there needs to be a JWT authentication enabled in Vault and needs to be enabled in GitLab as well. And Vault needs to be configured and needs to be able to communicate properly. You need to be able to communicate to Vault through a public IP. So the Vault needs to be exposed externally. And just to consider Vault can be run on Kubernetes as well. So it does require some setup with Vault. The piece that we've introduced is just being able to easily call Vault with certain syntax once Vault has already been set up. And I'm planning to make a demo video on this on how to set up Vault properly and gathering some resources and editing documentation. But for now, I just want to highlight this feature. So why does this matter for our customers? So it adds extra protection to GitLab environment variables by having a secret storage, which is Vault. And number two, it makes it easier to actually access these protected environment variables from Vault by using specific syntax. And for us, it's good because the user it makes the user experience a lot easier, a lot better. But also it adds another great integration to our portfolio and HashiCorp is one of our partners. So it helps us keep integrating different features, different HashiCorp features like Vault. Here's some information. And now let me just let me just show you this. So let me share the terminal real quick. Okay, so in my Vault, there's a few things that I have set up. So I have a policy and my policy says that within this path, I can read and list secrets. So this is my path on Vault OPS data staging secret and within that path, I have different key value pairs. And I'm only able to read and list it based off that policy. Then I have a role. And this role, what it does is it maps to my project ID. So this is only accessible from within my project. And it uses my policy that I've defined up here. So within this project on this space, I can read and list everything in this path. So that's my role. Then I have a key value pair. So I've created a key value pair with a key foo and a value world. And this is secret to the Vault. And it's using kvv2. So the kvv2 secret engine. And then from there, so now we want to be able to access this from GitLab. So how do we do that? So let me share Chrome again. So I've created this project. That's my simply simple notes Vaulted. And a few things to check out. So in the CI YAML, in my deploy staging job, I use this secret syntax. So I'm using the secret syntax. And I'm saying make an environment variable named foo and populate it with what's in staging, secret, and the value the key foo at ops, which is the head directory, which is slash ops, slash staging, slash secret. And then the key is foo. So it's going to populate this with a file that it extracts. And that file is going to contain the value of foo. And then here I'm going to echo foo so you can see what it is. And I'm going to cat foo so you can see what's in that file. So I'll show you the location of the file and the file. And then you can see there's three environment variables required. One is the URL for the Vault server. One is the off-road that I'm using. And one is the off-path, which is JWT because it is a JWT authentication. So this will be pretty standard. That needs to be set up anytime you're extracting secrets. So now let me go ahead and show you the job. So if you look at this job, you can see that if I echo foo, it gives me a path to a temporary file, a temporary directory with the file foo in it. And you can see that once I cat foo, you can see world, which is the value of that key. So that's pretty much the Vault integration and new syntax in a nutshell. And I'm happy to have shown you these features from 13.4. So please reach out to us on the technical marketing slack and let me know if you're interested in any demos on these features and highlighting these main parts. Thank you. So here are with the Atlassian developer page, the developer.alassian.com. This is where we are going to set up Atlassian as Omnia provider. What we do is go to this URL up here and then we're going to create a new app. The app name GitLab. Great. Go ahead and create that. And then this is going to give us a client ID and a secret. So we're going to go make sure that we copy both of these. And left sidebar we'll see under APIs and features. We'll click OAuth2.0. And then there we will call back URL. We'll enter our URL. We can see that's an example right here. So you'll switch that out. Go ahead and save those changes. Our app doesn't have any APIs. And then we'll go ahead and click add. Go to the Jira platform recipe API. Click that. Can figure. And then we'll add the view Jira issue data. We'll also add view user profiles which has already been added. So we don't need to remove that. And then create and manage issues. And we have our app for the GitLab configuration on your GitLab server. Open the configuration file. You either use omnibus or source installation either these codes. For the provider configuration for Atlassian. Same thing you'll use omnibus or source installation code that's specific to each. And then you'll change your client ID and your client secret to the client credentials that you received in the application registration steps we went through. Save that configuration file and then reconfigure or restart GitLab for the changes to take effect. If you install a GitLab via omnibus or from source respectively. And then on the sign in page there should now be an Atlassian icon where the regular sign in form is located and click the icon to begin the authentication process. And if everything goes right the user is signed in to GitLab using their Atlassian credentials. Thanks for watching and I hope you enjoyed. Please hit the subscribe button. And remember here at GitLab everyone can contribute.