Grrrr DevOps Pipeline... premier gros crash 😤/en - Historique des versions

Lli : Page créée avec « WorkArround $azAccountsVersion = (Get-Module -ListAvailable -Name Az.Accounts | Sort-Object Version -Descending | Select-Object -First 1).Version $dexResourceUrl = 'https://database.windows.net/' if ($azAccountsVersion -ge [Version]'5.0.0') { write-host "Az.Accounts 5.0.0 and above" $AccessTokenSecure = (Get-AzAccessToken -ResourceUrl $dexResourceUrl).Token $token = ConvertFrom-SecureString -Sec... »

2025-06-05T12:55:39Z

Page créée avec « </syntaxhighlight>WorkArround<syntaxhighlight lang="powershell"> $azAccountsVersion = (Get-Module -ListAvailable -Name Az.Accounts | Sort-Object Version -Descending | Select-Object -First 1).Version $dexResourceUrl = 'https://database.windows.net/' if ($azAccountsVersion -ge [Version]'5.0.0') { write-host "Az.Accounts 5.0.0 and above" $AccessTokenSecure = (Get-AzAccessToken -ResourceUrl $dexResourceUrl).Token $token = ConvertFrom-SecureString -Sec... »

← Version précédente		Version du 5 juin 2025 à 14:55
Ligne 30 :		Ligne 30 :
	Note : https://aka.ms/azps-changewarnings		Note : https://aka.ms/azps-changewarnings

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~
	</syntaxhighlight>WorkArround<syntaxhighlight lang="powershell">		</syntaxhighlight>WorkArround<syntaxhighlight lang="powershell">
	$azAccountsVersion = (Get-Module -ListAvailable -Name Az.Accounts \| Sort-Object Version -Descending \| Select-Object -First 1).Version		$azAccountsVersion = (Get-Module -ListAvailable -Name Az.Accounts \| Sort-Object Version -Descending \| Select-Object -First 1).Version
Ligne 43 :		Ligne 42 :
	}		}
	</syntaxhighlight>		</syntaxhighlight>
	~~</div>~~
	[[Catégorie:Boîte à idées]]		[[Catégorie:Boîte à idées]]

Lli : Page créée avec «  get-azaccesstoken WARNING: Upcoming breaking changes in the cmdlet 'Get-AzAccessToken' : The Token property of the output type will be changed from String to SecureString. Add the [-AsSecureString] switch to avoid the impact of this upcoming breaking change. - The change is expected to take effect in Az version : '14.0.0' - The change is expected to take effect in Az.Accounts version : '5.0.0' Note : https://aka.ms/azps-changewarnings »

2025-06-05T12:55:30Z

Page créée avec « <syntaxhighlight lang="pwsh"> get-azaccesstoken WARNING: Upcoming breaking changes in the cmdlet 'Get-AzAccessToken' : The Token property of the output type will be changed from String to SecureString. Add the [-AsSecureString] switch to avoid the impact of this upcoming breaking change. - The change is expected to take effect in Az version : '14.0.0' - The change is expected to take effect in Az.Accounts version : '5.0.0' Note : https://aka.ms/azps-changewarnings »

← Version précédente		Version du 5 juin 2025 à 14:55
Ligne 22 :		Ligne 22 :
	Here’s the warning we should have taken seriously:		Here’s the warning we should have taken seriously:

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~
	<syntaxhighlight lang="pwsh">		<syntaxhighlight lang="pwsh">
	get-azaccesstoken		get-azaccesstoken
Ligne 30 :		Ligne 29 :
	- The change is expected to take effect in Az.Accounts version : '5.0.0'		- The change is expected to take effect in Az.Accounts version : '5.0.0'
	Note : https://aka.ms/azps-changewarnings		Note : https://aka.ms/azps-changewarnings
	~~</div>~~

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Lli : Page créée avec « Here’s the warning we should have taken seriously: »

2025-06-05T12:55:21Z

Page créée avec « Here’s the warning we should have taken seriously: »

← Version précédente		Version du 5 juin 2025 à 14:55
Ligne 20 :		Ligne 20 :
	🔧 Fix: you need to add the -AsPlainText parameter in some cases, or completely revise how the token is handled depending on the module version used.		🔧 Fix: you need to add the -AsPlainText parameter in some cases, or completely revise how the token is handled depending on the module version used.

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~		Here’s the warning we should have taken seriously:
	~~Voici le~~ warning ~~qu’on aurait dû prendre au sérieux~~ :
	~~</div>~~

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Lli : Page créée avec « 🔧 Fix: you need to add the -AsPlainText parameter in some cases, or completely revise how the token is handled depending on the module version used. »

2025-06-05T12:55:13Z

Page créée avec « 🔧 Fix: you need to add the -AsPlainText parameter in some cases, or completely revise how the token is handled depending on the module version used. »

← Version précédente		Version du 5 juin 2025 à 14:55
Ligne 18 :		Ligne 18 :
	🎓 Lesson learned: never ignore warnings… even if they're buried deep in the logs.		🎓 Lesson learned: never ignore warnings… even if they're buried deep in the logs.

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~		🔧 Fix: you need to add the -AsPlainText parameter in some cases, or completely revise how the token is handled depending on the module version used.
	🔧 Fix : ~~il faut ajouter le paramètre <code>~~-AsPlainText~~</code> dans certains cas ou revoir complètement la gestion du~~ token ~~selon le~~ module ~~utilisé~~.
	~~</div>~~

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Lli : Page créée avec « 🎓 Lesson learned: never ignore warnings… even if they're buried deep in the logs. »

2025-06-05T12:54:58Z

Page créée avec « 🎓 Lesson learned: never ignore warnings… even if they're buried deep in the logs. »

← Version précédente		Version du 5 juin 2025 à 14:54
Ligne 16 :		Ligne 16 :
	The worst part? Since everything runs in the backend, we don’t get any warnings, so no one saw it coming. It was only after the exports started failing that we realized what was going on.		The worst part? Since everything runs in the backend, we don’t get any warnings, so no one saw it coming. It was only after the exports started failing that we realized what was going on.

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~		🎓 Lesson learned: never ignore warnings… even if they're buried deep in the logs.
	🎓 ~~Leçon apprise~~ : ~~ne jamais ignorer les~~ warnings… ~~même s’ils sont planqués dans les~~ logs.
	~~</div>~~

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Lli : Page créée avec « The worst part? Since everything runs in the backend, we don’t get any warnings, so no one saw it coming. It was only after the exports started failing that we realized what was going on. »

2025-06-05T12:54:43Z

Page créée avec « The worst part? Since everything runs in the backend, we don’t get any warnings, so no one saw it coming. It was only after the exports started failing that we realized what was going on. »

← Version précédente		Version du 5 juin 2025 à 14:54
Ligne 14 :		Ligne 14 :
	The result? All the older functions that handle these tokens can’t read them anymore, and everything breaks. In production. 😩		The result? All the older functions that handle these tokens can’t read them anymore, and everything breaks. In production. 😩

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~		The worst part? Since everything runs in the backend, we don’t get any warnings, so no one saw it coming. It was only after the exports started failing that we realized what was going on.
	~~Le pire~~ ? ~~Comme tout tourne dans un~~ backend, ~~'''on ne remonte pas les~~ warnings~~'''~~, ~~donc '''personne ne l’a vu venir'''~~. ~~C’est seulement une fois que les~~ exports ~~sont tombés en erreur qu’on a compris~~.
	~~</div>~~

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Lli : Page créée avec « And this Sunday… boom 💥: they updated the Az.Accounts module from version 4 to 5, with a major breaking change: The token is no longer returned as a String, but as a SecureString! The result? All the older functions that handle these tokens can’t read them anymore, and everything breaks. In production. 😩 »

2025-06-05T12:54:27Z

Page créée avec « And this Sunday… boom 💥: they updated the Az.Accounts module from version 4 to 5, with a major breaking change: The token is no longer returned as a String, but as a SecureString! The result? All the older functions that handle these tokens can’t read them anymore, and everything breaks. In production. 😩 »

← Version précédente		Version du 5 juin 2025 à 14:54
Ligne 8 :		Ligne 8 :
	The catch? Microsoft continuously updates their backend. So the Azure Pipeline pool that runs our PowerShell scripts gets updated automatically, without any action on our part.		The catch? Microsoft continuously updates their backend. So the Azure Pipeline pool that runs our PowerShell scripts gets updated automatically, without any action on our part.

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~		And this Sunday… boom 💥: they updated the Az.Accounts module from version 4 to 5, with a major breaking change:
	~~Et ce dimanche… '''patatras~~ 💥~~'''~~ : ~~ils ont mis à jour le module '''~~Az.Accounts ~~de la~~ version 4 ~~vers la~~ 5~~'''~~, ~~avec un '''~~breaking change ~~majeur'''~~ :~~<blockquote>Le~~ token ~~n’est plus retourné en <code>~~String~~</code>~~, ~~mais en <code>~~SecureString~~</code>~~ !~~</blockquote>Résultat~~ ? ~~Toutes les fonctions plus anciennes qui manipulent ces~~ tokens ~~n’arrivent plus à les lire~~, ~~et '''ça casse tout~~. ~~En prod~~.~~'''~~ 😩
	~~</div>~~		The token is no longer returned as a String, but as a SecureString!

			The result? All the older functions that handle these tokens can’t read them anymore, and everything breaks. In production. 😩

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Lli : Page créée avec « The catch? Microsoft continuously updates their backend. So the Azure Pipeline pool that runs our PowerShell scripts gets updated automatically, without any action on our part. »

2025-06-05T12:54:08Z

Page créée avec « The catch? Microsoft continuously updates their backend. So the Azure Pipeline pool that runs our PowerShell scripts gets updated automatically, without any action on our part. »

← Version précédente		Version du 5 juin 2025 à 14:54
Ligne 6 :		Ligne 6 :
	And for that, '''we use the token obtained with the Get-AzAccessToken function<code>Get-AzAccessToken</code>'''..		And for that, '''we use the token obtained with the Get-AzAccessToken function<code>Get-AzAccessToken</code>'''..

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~		The catch? Microsoft continuously updates their backend. So the Azure Pipeline pool that runs our PowerShell scripts gets updated automatically, without any action on our part.
	~~Le hic~~ ? Microsoft ~~met à jour en continu leur~~ backend. ~~Donc le '''~~pool ~~d’Azure Pipeline''' qui exécute nos~~ scripts ~~PowerShell est mis à jour automatiquement~~, ~~sans intervention de notre~~ part.
	~~</div>~~

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Lli : Page créée avec « And for that, '''we use the token obtained with the Get-AzAccessToken function`Get-AzAccessToken`'''.. »

2025-06-05T12:53:48Z

Page créée avec « And for that, '''we use the token obtained with the Get-AzAccessToken function<code>Get-AzAccessToken</code>'''.. »

← Version précédente		Version du 5 juin 2025 à 14:53
Ligne 4 :		Ligne 4 :
	We work in a fullstack DevOps team, with scripts that call SQL procedures in thousands of Azure SQL databases, whether for maintenance, exports, cleanup… you know, the usual stuff.		We work in a fullstack DevOps team, with scripts that call SQL procedures in thousands of Azure SQL databases, whether for maintenance, exports, cleanup… you know, the usual stuff.

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~		And for that, '''we use the token obtained with the Get-AzAccessToken function<code>Get-AzAccessToken</code>'''..
	~~Et pour ça~~, '''~~on utilise le~~ token ~~obtenu avec la fonction~~ <code>Get-AzAccessToken</code>'''.
	~~</div>~~

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Lli : Page créée avec « We work in a fullstack DevOps team, with scripts that call SQL procedures in thousands of Azure SQL databases, whether for maintenance, exports, cleanup… you know, the usual stuff. »

2025-06-05T12:53:10Z

Page créée avec « We work in a fullstack DevOps team, with scripts that call SQL procedures in thousands of Azure SQL databases, whether for maintenance, exports, cleanup… you know, the usual stuff. »

← Version précédente		Version du 5 juin 2025 à 14:53
Ligne 2 :		Ligne 2 :
	I knew Microsoft had given a warning… but as usual, no one really took it seriously 😅		I knew Microsoft had given a warning… but as usual, no one really took it seriously 😅

	~~<div lang="fr" dir="ltr" class="mw-content-ltr">~~		We work in a fullstack DevOps team, with scripts that call SQL procedures in thousands of Azure SQL databases, whether for maintenance, exports, cleanup… you know, the usual stuff.
	~~On bosse dans une équipe ''~~fullstack DevOps'', ~~avec des~~ scripts ~~qui appellent des procédures~~ SQL ~~dans des '''milliers de bases~~ Azure SQL~~'''~~, ~~que ce soit pour de la~~ maintenance, ~~des~~ exports, ~~du nettoyage… bref~~, ~~du classique~~.
	~~</div>~~

	<div lang="fr" dir="ltr" class="mw-content-ltr">		<div lang="fr" dir="ltr" class="mw-content-ltr">

Grrrr DevOps Pipeline... premier gros crash 😤/en - Historique des versions

Lli : Page créée avec « Here’s the warning we should have taken seriously: »

Lli : Page créée avec « 🔧 Fix: you need to add the -AsPlainText parameter in some cases, or completely revise how the token is handled depending on the module version used. »

Lli : Page créée avec « 🎓 Lesson learned: never ignore warnings… even if they're buried deep in the logs. »

Lli : Page créée avec « The worst part? Since everything runs in the backend, we don’t get any warnings, so no one saw it coming. It was only after the exports started failing that we realized what was going on. »

Lli : Page créée avec « The catch? Microsoft continuously updates their backend. So the Azure Pipeline pool that runs our PowerShell scripts gets updated automatically, without any action on our part. »

Lli : Page créée avec « And for that, '''we use the token obtained with the Get-AzAccessToken functionGet-AzAccessToken'''.. »