forked from asciidoctor/jekyll-asciidoc-quickstart
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfeed.xml
More file actions
4036 lines (3950 loc) · 328 KB
/
feed.xml
File metadata and controls
4036 lines (3950 loc) · 328 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>A bit of everything</title>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
<link>https://r3dlin3.github.io/</link>
<description>A bit of everything</description>
<pubDate>Thu, 22 Dec 2022 20:20:10 +0000</pubDate>
<item>
<title>Fun avec Salesforce Developer edition</title>
<link>/2022/03/14/salesforce-developer-edition/</link>
<guid isPermaLink="true">/2022/03/14/salesforce-developer-edition/</guid>
<description><div class="sect1">
<h2 id="introduction"><a class="anchor" href="#introduction"></a><a class="link" href="#introduction">Introduction</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Salesforce permet très facilement d&#8217;avoir une instance développeur pour tester certaines fonctionnalités du produit.
Comme Salesforce est très utilisé par les entreprises, il s&#8217;agit d&#8217;une application représentative lors de nos démos pour du SSO, du provisioning, etc.</p>
</div>
<div class="paragraph">
<p>La documentation de Salesforce est assez complète mais elle ne relate pas toujours des spécificités de l&#8217;édition développeur.
Voici quelques notes pour travailler avec Salesforce</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="authentification_api"><a class="anchor" href="#authentification_api"></a><a class="link" href="#authentification_api">Authentification API</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Pour utiliser les API, on doit obtenir un jeton d&#8217;accès ou <em>access token</em>.
Salesforce utilise OAuth2.0 et pour l&#8217;instant, j&#8217;ai réussi à faire fonctionner 2 méthodes:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Authorization Code</p>
</li>
<li>
<p>Refresh Token</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>Salesforce définit la notion d'"Application connectée".
Pour créer une application, dans la partie Setup en Lightning, sous "Administration", aller dans <strong>Apps</strong> &gt; <strong>App Manager</strong> et cliquer sur le bouton <strong>New Connected App</strong>.</p>
</div>
<div class="paragraph">
<p>Plus tard, il est possible d&#8217;éditer une application en allant, cette fois-ci en <strong>Classic</strong>, <strong>Build</strong> &gt; <strong>Create</strong> &gt; <strong>Apps</strong>, puis <strong>Edit</strong> sur l&#8217;application choisie.</p>
</div>
<div class="paragraph">
<p>Ainsi, il est possible de générer un <em>Client ID</em> et un <em>Client Secret</em> en cliquant sur le bouton <strong>Manage Consumer Details</strong>.</p>
</div>
<div class="sect2">
<h3 id="authorization_code"><a class="anchor" href="#authorization_code"></a><a class="link" href="#authorization_code">Authorization Code</a></h3>
<div class="paragraph">
<p>Postman supporte cette méthode, ce qui est très pratique.
Il y a un certain nombre de condition à remplir:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>L&#8217;URL de redirection (<em>Callback URL</em>) est donné par Postman (<a href="https://oauth.pstmn.io/v1/callback" class="bare">https://oauth.pstmn.io/v1/callback</a>)</p>
</li>
<li>
<p>Utiliser le <em>Client ID</em> et <em>Client Secret</em> générés précédemment</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>Même pour une instance Développeur, Les URL sont:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Authorization/Authentification: <a href="https://login.salesforce.com/services/oauth2/authorize" class="bare">https://login.salesforce.com/services/oauth2/authorize</a></p>
</li>
<li>
<p>Token : <a href="https://login.salesforce.com/services/oauth2/token" class="bare">https://login.salesforce.com/services/oauth2/token</a></p>
</li>
</ul>
</div>
<div class="imageblock text-center">
<div class="content">
<img src="https://r3dlin3.github.io/assets/img/2022-03-14-salesforce-developer-edition/Postman-AuthorizationCode.png" alt="Echanger un code">
</div>
</div>
</div>
<div class="sect2">
<h3 id="refresh_token"><a class="anchor" href="#refresh_token"></a><a class="link" href="#refresh_token">Refresh Token</a></h3>
<div class="paragraph">
<p>La génération d&#8217;un Refresh Token est un peu fastidieux mais permet des communications "Machine à Machine".</p>
</div>
<div class="paragraph">
<p>La première étape consiste à créer une application avec comme URL de redirection <a href="https://login.salesforce.com/" class="bare">https://login.salesforce.com/</a>.
L&#8217;application doit avoir un scope "Perform requests at any time (refresh_token, offline_access)".</p>
</div>
<div class="paragraph">
<p>Créer l&#8217;URL de connexion de la forme
<code><a href="https://login.salesforce.com/services/oauth2/authorize?response_type=code&amp;client_id=&lt;clientId&gt;&amp;redirect_uri=https://login.salesforce.com/&amp;scope=offline_access" class="bare">https://login.salesforce.com/services/oauth2/authorize?response_type=code&amp;client_id=&lt;clientId&gt;&amp;redirect_uri=https://login.salesforce.com/&amp;scope=offline_access</a></code> en remplaçant <code>&lt;clientId&gt;</code> par celui de l&#8217;application générée.</p>
</div>
<div class="paragraph">
<p>En ouvrant cette URL dans le navigateur, après authentification et consentement, le navigateur est redirigé vers <a href="https://login.salesforce.com/" class="bare">https://login.salesforce.com/</a> avec dans l&#8217;URL un paramètre <code>code</code>.</p>
</div>
<div class="paragraph">
<p>Récupéré la valeur du paramètre <code>code</code>. <strong>Attention</strong>, la valeur est URL-encodée. Il faut alors la URL-décoder (Notepad++ est ton ami par exemple).</p>
</div>
<div class="paragraph">
<p>A ce stade, il faut échanger le code contre des tokens. Pour ce faire, il suffit de faire un <code>POST</code> sur <a href="https://login.salesforce.com/services/oauth2/token" class="bare">https://login.salesforce.com/services/oauth2/token</a> avec les paramètres:</p>
</div>
<div class="ulist">
<ul>
<li>
<p><code>client_id</code></p>
</li>
<li>
<p><code>client_secret</code></p>
</li>
<li>
<p><code>redirect_uri</code> = <code><a href="https://login.salesforce.com/" class="bare">https://login.salesforce.com/</a></code></p>
</li>
<li>
<p><code>grant_type</code> = <code>authorization_code</code></p>
</li>
<li>
<p><code>code</code></p>
</li>
</ul>
</div>
<div class="imageblock text-center">
<div class="content">
<img src="https://r3dlin3.github.io/assets/img/2022-03-14-salesforce-developer-edition/Postman-RefreshToken.png" alt="Echanger un code">
</div>
</div>
<div class="paragraph">
<p>En retour, un Refresh Token sera donné.</p>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="etendre_un_objet"><a class="anchor" href="#etendre_un_objet"></a><a class="link" href="#etendre_un_objet">Etendre un objet</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Il est très facile d&#8217;étendre un objet dans Salesforce.
Sans rentrer dans les considération de vue, de sécurité, etc. on peut ajouter un nouvel attribut (ex: une référence externe) en allant dans <strong>Object Manager</strong>, puis pour l&#8217;objet souhaité <strong>Fields &amp; Relationships</strong>.</p>
</div>
<div class="imageblock text-center">
<div class="content">
<img src="https://r3dlin3.github.io/assets/img/2022-03-14-salesforce-developer-edition/Salesforce-ref.png" alt="Echanger un code">
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="api_sobjects"><a class="anchor" href="#api_sobjects"></a><a class="link" href="#api_sobjects">API SObjects</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>L&#8217;API SObjects permet de manipuler les objets Salesforce:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Description d&#8217;un objet (ses attributs)</p>
</li>
<li>
<p>Création d&#8217;un objet</p>
</li>
<li>
<p>Détail d&#8217;un objet</p>
</li>
<li>
<p>Récupération d&#8217;un objet par référence externe</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>L&#8217;URL de base est construite de la façon suivante</p>
</div>
<div class="listingblock">
<div class="content">
<pre>https://&lt;instance&gt;.develop.my.salesforce.com/services/data/&lt;version&gt;/sobjects/&lt;Objet&gt;/&lt;Méthode&gt;</pre>
</div>
</div>
<div class="paragraph">
<p>En étant connecté à Salesforce, on accès par exemple à:</p>
</div>
<div class="listingblock">
<div class="content">
<pre>https://&lt;instance&gt;.develop.lightning.force.com/one/one.app</pre>
</div>
</div>
<div class="paragraph">
<p>Les versions sont données en accédant à <code><a href="https://&lt;instance&gt;.develop.my.salesforce.com/services/data/" class="bare">https://&lt;instance&gt;.develop.my.salesforce.com/services/data/</a></code>. Au moment de la rédaction de cet article, la dernière version est <code>v56.0</code>.</p>
</div>
<div class="paragraph">
<p>Pour obtenir la liste des attributs d&#8217;un compte, on peut alors accéder à&nbsp;:</p>
</div>
<div class="listingblock">
<div class="content">
<pre>https://&lt;instance&gt;.develop.my.salesforce.com/services/data/&lt;version&gt;/sobjects/Account/describe</pre>
</div>
</div>
<div class="paragraph">
<p>Il est possible d&#8217;obtenir un objet par sa référence interne (<code>/sobjects/Account/&lt;AccountId</code>) ou une référence externe (<code>/sobjects/Account/Business_Partner_Code__c/TEST1</code>).</p>
</div>
</div>
</div>
<div class="sect1">
<h2 id="api_de_requête"><a class="anchor" href="#api_de_requête"></a><a class="link" href="#api_de_requête">API de requête</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Pour requêter (lister) des objets, Salesforce a défini le Salesforce Object Query Language (SOQL) qui s&#8217;apparente fortement au SQL.</p>
</div>
<div class="paragraph">
<p>Pour lister les comptes on peut par exemple exécuter</p>
</div>
<div class="listingblock">
<div class="content">
<pre>https://&lt;instance&gt;.develop.my.salesforce.com/services/data/&lt;version&gt;/query?q=SELECT Name FROM Account WHERE Name='TEST1'</pre>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="api_composite"><a class="anchor" href="#api_composite"></a><a class="link" href="#api_composite">API Composite</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Il est possible de chaîner des requêtes qui peuvent ainsi se référencer les unes avec les autres.</p>
</div>
<div class="paragraph">
<p>On peut donc imaginer&nbsp;:</p>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Rechercher un compte</p>
</li>
<li>
<p>Créer un contact dans ce compte</p>
</li>
<li>
<p>Créer un utilisateur associé</p>
</li>
</ol>
</div>
<div class="paragraph">
<p>La requête composite est rendue "transactionnelle" avec le flag <code>allOrNone</code>.</p>
</div>
<div class="paragraph">
<p>Ci-dessous</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="JSON">{
"allOrNone": true,
"compositeRequest": [
{
"method": "GET",
"url": "/services/data/v56.0/sobjects/Account/Business_Partner_Code__c/TEST1",
"referenceId": "refAccount"
},
{
"method": "POST",
"url": "/services/data/v56.0/sobjects/Contact",
"referenceId": "xxx",
"body": {
"LastName": "Fernandez",
"FirstName": "Linda",
"AccountId": "@{refAccount.Id}",
"Email": "XXX@yopmail.com"
}
},
{
"method": "POST",
"url": "/services/data/v56.0/sobjects/User",
"referenceId": "newUser",
"body": {
"LastName": "Fernandez",
"FirstName": "Linda",
"ContactId": "@{newContact.id}",
"Email": "XXX@yopmail.com",
"EmailEncodingKey": "UTF-8",
"ProfileId": "00eDn000001vctqIAA",
"Username": "XXX@yopmail.com",
"Alias": "LFernand",
"TimeZoneSidKey": "America/Los_Angeles",
"LocaleSidKey": "en_US",
"LanguageLocaleKey": "en_US"
}
}
]
}</code></pre>
</div>
</div>
<div class="admonitionblock warning">
<table>
<tr>
<td class="icon">
<i class="fa icon-warning" title="Warning"></i>
</td>
<td class="content">
La casse est importante et pas toujours cohérente. Ainsi, dans le contact créé, il faut utiliser <code>id</code> mais pour récupérer l&#8217;Id du compte précédemment recherché, il faut utiliser <code>Id</code>.
</td>
</tr>
</table>
</div>
<div class="admonitionblock tip">
<table>
<tr>
<td class="icon">
<i class="fa icon-tip" title="Tip"></i>
</td>
<td class="content">
Le retour de la requête composite donne le retour de chaque requête. En créant sa requête composite progressivement, on peut voir le retour et y faire référence plus facilement.
</td>
</tr>
</table>
</div>
</div>
</div>
<div class="sect1">
<h2 id="conclusion"><a class="anchor" href="#conclusion"></a><a class="link" href="#conclusion">Conclusion</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Salesforce dispose d&#8217;une documentation propre assez riche et d&#8217;une multitude de contenu par sa communauté. Voici ma contribution 😆.</p>
</div>
</div>
</div></description>
<pubDate>Mon, 14 Mar 2022 00:00:00 +0000</pubDate>
</item>
<item>
<title>Bicep et extension DSC pour VM [fr]</title>
<link>/2022/03/14/bicep-vm-dsc-extension-fr/</link>
<guid isPermaLink="true">/2022/03/14/bicep-vm-dsc-extension-fr/</guid>
<description><div class="sect1">
<h2 id="introduction"><a class="anchor" href="#introduction"></a><a class="link" href="#introduction">Introduction</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Je n&#8217;ai jamais eu le temps de jouer avec <a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview?tabs=bicep">Bicep</a> et j&#8217;étais coincé avec les modèles ARM.
Suite à un <a href="https://faun.pub/format-and-mount-a-vm-disk-using-terraform-in-azure-a622313d43e5">article de blog</a>, j&#8217;ai décidé de documenter une méthode alternative s&#8217;appuyant sur DSC et d&#8217;essayer Bicep en même temps : déployer une VM avec plusieurs disques, les formater et les attacher à la VM.
Bien sûr, DSC peut être utilisé pour des choses plus puissantes, de l&#8217;installation du <a href="https://github.com/chocolatey/cChoco">package choco</a> à l&#8217;installation et à la gestion de <a href="https://github.com/dsccommunity/SqlServerDsc">SQL Server</a>.</p>
</div>
<div class="paragraph">
<p>L&#8217;utilisation de DSC par rapport à du PowerShell seul est un débat sans fin. Chaque approche a ses pours et ses contres. Personnellement, j&#8217;ai été séduit par :</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Le nombre de modules existants</p>
</li>
<li>
<p>L&#8217;idempotence de DSC</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>Les autres arguments sont :</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Capacité de reporting/audit avec DSC</p>
</li>
<li>
<p>Intégration avec <a href="https://docs.microsoft.com/en-us/azure/automation/automation-dsc-overview">Azure Automation</a></p>
</li>
</ul>
</div>
<div id="toc" class="toc">
<div id="toctitle" class="title">Table des matières</div>
<ul class="sectlevel1">
<li><a href="#introduction">Introduction</a></li>
<li><a href="#prérequis">Prérequis</a>
<ul class="sectlevel2">
<li><a href="#cli_bicep">CLI Bicep</a></li>
<li><a href="#groupes_de_ressources_azure">Groupes de ressources Azure</a></li>
<li><a href="#compte_de_stockage_azure">Compte de stockage Azure</a></li>
</ul>
</li>
<li><a href="#powershell_dsc">PowerShell DSC</a>
<ul class="sectlevel2">
<li><a href="#préparation_du_package">Préparation du package</a></li>
<li><a href="#publication_du_package">Publication du package</a></li>
</ul>
</li>
<li><a href="#vm_et_extension_dsc">VM et extension DSC</a></li>
<li><a href="#conclusion">Conclusion</a></li>
</ul>
</div>
</div>
</div>
<div class="sect1">
<h2 id="prérequis"><a class="anchor" href="#prérequis"></a><a class="link" href="#prérequis">Prérequis</a></h2>
<div class="sectionbody">
<div class="sect2">
<h3 id="cli_bicep"><a class="anchor" href="#cli_bicep"></a><a class="link" href="#cli_bicep">CLI Bicep</a></h3>
<div class="paragraph">
<p>L&#8217;outil de commande en ligne (CLI) Bicep existe en tant qu&#8217;extension d&#8217;Azure CLI ou en tant que CLI autonome.
J&#8217;ai fait le choix d&#8217;utiliser l&#8217;extension Azure CLI.
Pour installer cette extension, la commande est plutôt simple :</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="cmd">az bicep install</code></pre>
</div>
</div>
</div>
<div class="sect2">
<h3 id="groupes_de_ressources_azure"><a class="anchor" href="#groupes_de_ressources_azure"></a><a class="link" href="#groupes_de_ressources_azure">Groupes de ressources Azure</a></h3>
<div class="paragraph">
<p>Les groupes de ressources sont nécessaires pour créer la VM par exemple.
Habituellement, j&#8217;aurais un groupe de ressources "commun" pour le compte de stockage ou un VNET et un groupe de ressources pour la machine virtuelle, car mon compte de stockage est partagé entre mes ressources.
Pour cet exemple, pour des raisons de simplicité, je n&#8217;utiliserai qu&#8217;un seul groupe de ressources. Pour le créer :</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="cmd">az group create --name my-rg --location francecentral</code></pre>
</div>
</div>
</div>
<div class="sect2">
<h3 id="compte_de_stockage_azure"><a class="anchor" href="#compte_de_stockage_azure"></a><a class="link" href="#compte_de_stockage_azure">Compte de stockage Azure</a></h3>
<div class="paragraph">
<p>Les scripts DSC doivent être disponibles pour la machine virtuelle.
Je crée un compte de stockage pour stocker les scripts mais le garde privé pour des raisons de sécurité.
Ainsi, les scripts ne sont pas accessibles sans authentification</p>
</div>
<div class="paragraph">
<p>Pour créer le compte de stockage, j&#8217;ai utilisé un fichier Bicep&nbsp;:</p>
</div>
<div class="listingblock">
<div class="title">prerequisites/main.bicep</div>
<div class="content">
<pre class="rouge highlight"><code data-lang="bicep">// cf. https://github.com/Azure/bicep/blob/main/docs/examples/101/storage-blob-container/main.bicep
param storageAccountName string
param containerName string = 'dsc'
param location string = resourceGroup().location
resource sa 'Microsoft.Storage/storageAccounts@2019-06-01' = {
name: storageAccountName
location: location
sku: {
name: 'Standard_LRS'
}
kind: 'StorageV2'
properties: {
accessTier: 'Hot'
}
}
resource container 'Microsoft.Storage/storageAccounts/blobServices/containers@2019-06-01' = {
name: '${sa.name}/default/${containerName}'
}</code></pre>
</div>
</div>
<div class="paragraph">
<p>Ensuite, je déploie le modèle&nbsp;:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="cmd">az deployment group create --resource-group my-rg --template-file prerequisites/main.bicep --parameters storageAccountName=mystorageaccount</code></pre>
</div>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="powershell_dsc"><a class="anchor" href="#powershell_dsc"></a><a class="link" href="#powershell_dsc">PowerShell DSC</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>DSC permet de décrire une configuration à appliquer.
Voici un exemple de configuration DSC qui :</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Active le bureau à distance</p>
</li>
<li>
<p>Monte le disque de données</p>
</li>
</ul>
</div>
<div class="listingblock">
<div class="title">dsc/common.ps1</div>
<div class="content">
<pre class="rouge highlight"><code data-lang="powershell"><span class="kr">Configuration</span><span class="w"> </span><span class="n">Common</span><span class="w">
</span><span class="p">{</span><span class="w">
</span><span class="kr">param</span><span class="w">
</span><span class="p">(</span><span class="w">
</span><span class="p">[</span><span class="n">Parameter</span><span class="p">()]</span><span class="w">
</span><span class="p">[</span><span class="n">System.String</span><span class="p">[]]</span><span class="w">
</span><span class="nv">$NodeName</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'localhost'</span><span class="w">
</span><span class="p">)</span><span class="w">
</span><span class="n">Import-DscResource</span><span class="w"> </span><span class="nt">-Module</span><span class="w"> </span><span class="nx">xRemoteDesktopAdmin</span><span class="w">
</span><span class="n">Import-DSCResource</span><span class="w"> </span><span class="nt">-ModuleName</span><span class="w"> </span><span class="nx">StorageDsc</span><span class="w">
</span><span class="n">Import-DSCResource</span><span class="w"> </span><span class="nt">-ModuleName</span><span class="w"> </span><span class="nx">xPendingReboot</span><span class="w">
</span><span class="n">Node</span><span class="w"> </span><span class="nv">$NodeName</span><span class="w">
</span><span class="p">{</span><span class="w">
</span><span class="n">LocalConfigurationManager</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">RebootNodeIfNeeded</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="bp">$true</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="c">#region RDP</span><span class="w">
</span><span class="n">xRemoteDesktopAdmin</span><span class="w"> </span><span class="nx">RemoteDesktopSettings</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">Ensure</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'Present'</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="c">#endregion</span><span class="w">
</span><span class="n">xPendingReboot</span><span class="w"> </span><span class="nx">Reboot1</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">Name</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'BeforeManageDisk'</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="c">#region Disk</span><span class="w">
</span><span class="kr">if</span><span class="w"> </span><span class="p">(</span><span class="n">Get-CimInstance</span><span class="w"> </span><span class="nt">-ClassName</span><span class="w"> </span><span class="nx">Win32_CDROMDrive</span><span class="p">)</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">OpticalDiskDriveLetter</span><span class="w"> </span><span class="nx">SetFirstOpticalDiskDriveLetterToZ</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">DiskId</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">1</span><span class="w">
</span><span class="n">DriveLetter</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'Z'</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="n">WaitForDisk</span><span class="w"> </span><span class="nx">Disk2</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">DiskId</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s2">"2"</span><span class="w">
</span><span class="n">RetryIntervalSec</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">10</span><span class="w">
</span><span class="n">RetryCount</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">3</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="n">Disk</span><span class="w"> </span><span class="nx">EVolume</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">DiskId</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s2">"2"</span><span class="w">
</span><span class="n">DriveLetter</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'E'</span><span class="w">
</span><span class="n">FSLabel</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'Data'</span><span class="w">
</span><span class="n">DependsOn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'[WaitForDisk]Disk2'</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="c">#endregion</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">}</span></code></pre>
</div>
</div>
<div class="paragraph">
<p>Une fois la configuration écrite, vous devez&nbsp;:</p>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Préparer un package</p>
</li>
<li>
<p>Publier le package</p>
</li>
</ol>
</div>
<div class="sect2">
<h3 id="préparation_du_package"><a class="anchor" href="#préparation_du_package"></a><a class="link" href="#préparation_du_package">Préparation du package</a></h3>
<div class="paragraph">
<p>Vous devez installer toutes les dépendances/modules sur votre ordinateur.
Dans mon cas&nbsp;:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="powershell"><span class="n">install-module</span><span class="w"> </span><span class="nx">xRemoteDesktopAdmin</span><span class="w">
</span><span class="n">Install-Module</span><span class="w"> </span><span class="nx">StorageDsc</span><span class="w">
</span><span class="n">Install-Module</span><span class="w"> </span><span class="nx">xPendingReboot</span></code></pre>
</div>
</div>
<div class="admonitionblock tip">
<table>
<tr>
<td class="icon">
<i class="fa icon-tip" title="Tip"></i>
</td>
<td class="content">
L&#8217;installation des modules permettra également la complétion dans VSCode.
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>Vous pouvez créer un package à publier quelque part (compte de stockage, GitHub, etc.) avec la commande suivante, ou ignorer ceci et passer directement à l&#8217;étape suivante&nbsp;:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="powershell"><span class="n">Publish-AzVMDscConfiguration</span><span class="w"> </span><span class="o">.</span><span class="nx">\common.ps1</span><span class="w"> </span><span class="nt">-OutputArchivePath</span><span class="w"> </span><span class="o">.</span><span class="nx">\common.ps1.zip</span></code></pre>
</div>
</div>
</div>
<div class="sect2">
<h3 id="publication_du_package"><a class="anchor" href="#publication_du_package"></a><a class="link" href="#publication_du_package">Publication du package</a></h3>
<div class="paragraph">
<p>Le module Az possède une cmdlet spécifique capable de créer le package et de le transférer directement dans un compte de stockage&nbsp;:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="powershell"><span class="n">Publish-AzVMDscConfiguration</span><span class="w"> </span><span class="o">.</span><span class="nx">\common.ps1</span><span class="w"> </span><span class="nt">-ResourceGroupName</span><span class="w"> </span><span class="s2">"my-rg"</span><span class="w"> </span><span class="nt">-StorageAccountName</span><span class="w"> </span><span class="s2">"mystorageaccount"</span><span class="w"> </span><span class="nt">-ContainerName</span><span class="w"> </span><span class="s2">"dsc"</span><span class="w"> </span><span class="nt">-verbose</span><span class="w"> </span><span class="nt">-force</span></code></pre>
</div>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="vm_et_extension_dsc"><a class="anchor" href="#vm_et_extension_dsc"></a><a class="link" href="#vm_et_extension_dsc">VM et extension DSC</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Une fois le package DSC prêt, nous pouvons déployer une VM.
Dans mon exemple, je réutilise un VNET existant.
Pour plus de commodité dans mes tests, j&#8217;ajouterai également une adresse IP publique, mais ce n&#8217;est bien sûr pas une bonne pratique.</p>
</div>
<div class="paragraph">
<p>Je vais me concentrer sur l&#8217;extension DSC à la fin du fichier Bicep. Tous les paramètres de l&#8217;extension sont décrits dans la <a href="https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/dsc-template">documentation Microsoft</a>.</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="bicep">resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
name: storageAccountName
}
var _artifactsLocationSasToken = stg.listServiceSAS('2021-04-01', {
canonicalizedResource: '/blob/${stg.name}/${containerName}'
signedResource: 'c'
signedProtocol: 'https'
signedPermission: 'r'
signedServices: 'b'
signedExpiry: dateTimeAdd(baseTime, 'PT1H')
}).serviceSasToken <i class="conum" data-value="1"></i><b>(1)</b>
resource dscExtension 'Microsoft.Compute/virtualMachines/extensions@2018-10-01' = {
location: location
parent: vm
name: 'Microsoft.Powershell.DSC'
properties: {
publisher: 'Microsoft.Powershell'
type: 'DSC'
typeHandlerVersion: '2.77'
autoUpgradeMinorVersion: true
settings: {
wmfVersion: 'latest'
configuration: {
url: '${stg.properties.primaryEndpoints.blob}${containerName}/common.ps1.zip' <i class="conum" data-value="2"></i><b>(2)</b>
script: 'common.ps1' <i class="conum" data-value="3"></i><b>(3)</b>
function: 'Common' <i class="conum" data-value="4"></i><b>(4)</b>
}
configurationArguments: {}
}
protectedSettings: {
configurationUrlSasToken: '?${_artifactsLocationSasToken}' <i class="conum" data-value="5"></i><b>(5)</b>
}
}
}</code></pre>
</div>
</div>
<div class="colist arabic">
<table>
<tr>
<td><i class="conum" data-value="1"></i><b>1</b></td>
<td>Cette fonction, telle que décrite dans la <a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-resource#list">doc</a> permet d&#8217;obtenir un jeton SAS, en fonction de paramètres. Cependant, ce Token SAS ne contient pas le '?' comme paramètre de requête (<em>query string</em>).</td>
</tr>
<tr>
<td><i class="conum" data-value="2"></i><b>2</b></td>
<td>URL construite à partir de l&#8217;URL du compte de stockage + le conteneur + l&#8217;archive générée précédemment. L&#8217;URL blob se termine par un '/', d&#8217;où la concaténation sans '/' supplémentaire.</td>
</tr>
<tr>
<td><i class="conum" data-value="3"></i><b>3</b></td>
<td>Nom du script DSC.</td>
</tr>
<tr>
<td><i class="conum" data-value="4"></i><b>4</b></td>
<td>Nom de la configuration.</td>
</tr>
<tr>
<td><i class="conum" data-value="5"></i><b>5</b></td>
<td>Petite astuce pour obtenir un paramètre de requête (<em>query string</em>).</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>Le fichier complet <code>main.bicep</code> est disponible <a href="/assets/examples/bicep-vm-dsc-extension/vm/main.bicep">ici</a>.</p>
</div>
<div class="paragraph">
<p>Je comprends qu&#8217;à l&#8217;heure actuelle, il n&#8217;y a pas de mécanisme intégré pour créer un fichier de paramètres et que les fichiers de paramètres sont simplement des fichiers de paramètres de modèle ARM, basé sur JSON.
J&#8217;ai utilisé un script trouvé dans un <a href="https://github.com/Azure/bicep/issues/399">bug GitHub</a> pour préparer mes paramètres&nbsp;:</p>
</div>
<div class="listingblock">
<div class="title">vm/main.parameters.json</div>
<div class="content">
<pre class="rouge highlight"><code data-lang="json"><span class="p">{</span><span class="w">
</span><span class="nl">"$schema"</span><span class="p">:</span><span class="w"> </span><span class="s2">"https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#"</span><span class="p">,</span><span class="w">
</span><span class="nl">"contentVersion"</span><span class="p">:</span><span class="w"> </span><span class="s2">"1.0.0.0"</span><span class="p">,</span><span class="w">
</span><span class="nl">"parameters"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"adminUsername"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"administrateur"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"adminPassword"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"mysuperpassword"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"virtualNetworkName"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"MyVNET"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"subnetName"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Subnet"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"storageAccountName"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"mystorageaccount"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"vmName"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"myvm"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"nicName"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"nic-myvm"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"publicIpName"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"pip-myvm"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"networkSecurityGroupName"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="s2">"nsg-myvm"</span><span class="w">
</span><span class="p">},</span><span class="w">
</span><span class="nl">"sizeOfEachDataDiskInGB"</span><span class="p">:</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="nl">"value"</span><span class="p">:</span><span class="w"> </span><span class="mi">128</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">}</span></code></pre>
</div>
</div>
<div class="paragraph">
<p>Finalement, on déploie le template Bicep avec les paramètres&nbsp;:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="cmd">az deployment group create --resource-group my-rg --template-file vm/main.bicep --parameters @vm/main.parameters.json</code></pre>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="conclusion"><a class="anchor" href="#conclusion"></a><a class="link" href="#conclusion">Conclusion</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>Voici un moyen simple d&#8217;obtenir une machine virtuelle avec un disque de données prêt à l&#8217;emploi.</p>
</div>
<div class="paragraph">
<p>Cet article était un bon moyen de tester Bicep et il est claire que Bicep est vraiment plus concis que les modèles ARM.
Pour autant, est-ce mieux?</p>
</div>
<div class="paragraph">
<p>J&#8217;aime la création automatique du graphe de dépendance entre les ressources, comme dans Terraform.
J&#8217;aime la façon de référencer les ressources existantes.</p>
</div>
<div class="paragraph">
<p>Je n&#8217;ai pas aimé la très longue liste de paramètres que je ne pouvais pas réduire dans VSCode.
J&#8217;ai cependant eu quelques problèmes de déploiement et j&#8217;étais heureux de voir le modèle ARM généré (grâce à la commande <code>build</code>) et de voir ce qui ne fonctionnait pas bien avec mon fichier Bicep.</p>
</div>
<div class="paragraph">
<p>En tout cas, Microsoft a vraiment poussé vers Bicep et a des modèles prêts à l&#8217;emploi qui sont très utiles.</p>
</div>
<div class="paragraph">
<p>Avec cet exemple, je n&#8217;ai pas testé les modules qui sont clairement un super ajout au langage, proche de Terraform, quand on connait les modèles imbriqués avec ARM.</p>
</div>
<div class="paragraph">
<p>Alors, je vais me prendre au jeu et continuer à travailler avec Bicep avec Azure&nbsp;!</p>
</div>
</div>
</div></description>
<pubDate>Mon, 14 Mar 2022 00:00:00 +0000</pubDate>
</item>
<item>
<title>Bicep and VM DSC Extension [eng]</title>
<link>/2022/03/13/bicep-vm-dsc-extension/</link>
<guid isPermaLink="true">/2022/03/13/bicep-vm-dsc-extension/</guid>
<description><div class="sect1">
<h2 id="introduction"><a class="anchor" href="#introduction"></a><a class="link" href="#introduction">Introduction</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>I never had the time to play with <a href="https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/overview?tabs=bicep">Bicep</a> and was stuck with ARM templates.
Following a <a href="https://faun.pub/format-and-mount-a-vm-disk-using-terraform-in-azure-a622313d43e5">blog post</a>, I decided to document what I was using with DSC and try Bicep at the same time: deploy a VM with multiple discs, format them and attach them to the VM.
Of course, DSC can be used for more powerful stuff, from installing <a href="https://github.com/chocolatey/cChoco">choco package</a> to installing and managing <a href="https://github.com/dsccommunity/SqlServerDsc">SQL Server</a>.</p>
</div>
<div class="paragraph">
<p>Using DSC vs. Plain PowerShell is an endless debate. Each approach has its own pros and cons. Personally, I was seduced by:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>The number of existing modules</p>
</li>
<li>
<p>The idempotency of DSC</p>
</li>
</ul>
</div>
<div class="paragraph">
<p>Other arguments are:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Reporting capacity/auditing with DSC</p>
</li>
<li>
<p>Integration with <a href="https://docs.microsoft.com/en-us/azure/automation/automation-dsc-overview">Azure Automation</a></p>
</li>
</ul>
</div>
<div id="toc" class="toc">
<div id="toctitle" class="title">Table des matières</div>
<ul class="sectlevel1">
<li><a href="#introduction">Introduction</a></li>
<li><a href="#prerequisites">Prerequisites</a>
<ul class="sectlevel2">
<li><a href="#bicep_cli">Bicep CLI</a></li>
<li><a href="#azure_resource_groups">Azure Resource groups</a></li>
<li><a href="#azure_storage_account">Azure Storage Account</a></li>
</ul>
</li>
<li><a href="#dsc">DSC</a>
<ul class="sectlevel2">
<li><a href="#preparation_of_the_package">Preparation of the package</a></li>
<li><a href="#publication_of_the_package">Publication of the package</a></li>
</ul>
</li>
<li><a href="#vm_and_dsc_extension">VM and DSC extension</a></li>
<li><a href="#conclusion">Conclusion</a></li>
</ul>
</div>
</div>
</div>
<div class="sect1">
<h2 id="prerequisites"><a class="anchor" href="#prerequisites"></a><a class="link" href="#prerequisites">Prerequisites</a></h2>
<div class="sectionbody">
<div class="sect2">
<h3 id="bicep_cli"><a class="anchor" href="#bicep_cli"></a><a class="link" href="#bicep_cli">Bicep CLI</a></h3>
<div class="paragraph">
<p>Bicep CLI exists either as an extension of Azure CLI or as a standalone CLI.
I made the choice of using the Azure CLI extension.
To install this extension, the command is rather simple:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="cmd">az bicep install</code></pre>
</div>
</div>
</div>
<div class="sect2">
<h3 id="azure_resource_groups"><a class="anchor" href="#azure_resource_groups"></a><a class="link" href="#azure_resource_groups">Azure Resource groups</a></h3>
<div class="paragraph">
<p>Resource groups are required to create the VM for instance.
Usually, I would have a "common" resource group for the storage account or a VNET, and a resource group for my VM, as my storage account is shared across my resources.
For this example, I will use only one resource group. To create it:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="cmd">az group create --name my-rg --location francecentral</code></pre>
</div>
</div>
</div>
<div class="sect2">
<h3 id="azure_storage_account"><a class="anchor" href="#azure_storage_account"></a><a class="link" href="#azure_storage_account">Azure Storage Account</a></h3>
<div class="paragraph">
<p>The DSC scripts must be available to the VM.
I create a Storage Account to store the scripts but keep them private for security reason.
Thus, the scripts are not accessible without authentication.</p>
</div>
<div class="paragraph">
<p>To create the storage account, I used a Bicep file:</p>
</div>
<div class="listingblock">
<div class="title">prerequisites/main.bicep</div>
<div class="content">
<pre class="rouge highlight"><code data-lang="bicep">// cf. https://github.com/Azure/bicep/blob/main/docs/examples/101/storage-blob-container/main.bicep
param storageAccountName string
param containerName string = 'dsc'
param location string = resourceGroup().location
resource sa 'Microsoft.Storage/storageAccounts@2019-06-01' = {
name: storageAccountName
location: location
sku: {
name: 'Standard_LRS'
}
kind: 'StorageV2'
properties: {
accessTier: 'Hot'
}
}
resource container 'Microsoft.Storage/storageAccounts/blobServices/containers@2019-06-01' = {
name: '${sa.name}/default/${containerName}'
}</code></pre>
</div>
</div>
<div class="paragraph">
<p>Then, I deploy the template:</p>
</div>
<div class="listingblock">
<div class="content">
<pre class="rouge highlight"><code data-lang="cmd">az deployment group create --resource-group my-rg --template-file prerequisites/main.bicep --parameters storageAccountName=mystorageaccount</code></pre>
</div>
</div>
</div>
</div>
</div>
<div class="sect1">
<h2 id="dsc"><a class="anchor" href="#dsc"></a><a class="link" href="#dsc">DSC</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>DSC allows you to describe a configuration to be applied.
Here is an example of DSC configuration that will:</p>
</div>
<div class="ulist">
<ul>
<li>
<p>Enable remote desktop</p>
</li>
<li>
<p>Mount the data disk</p>
</li>
</ul>
</div>
<div class="listingblock">
<div class="title">dsc/common.ps1</div>
<div class="content">
<pre class="rouge highlight"><code data-lang="powershell"><span class="kr">Configuration</span><span class="w"> </span><span class="n">Common</span><span class="w">
</span><span class="p">{</span><span class="w">
</span><span class="kr">param</span><span class="w">
</span><span class="p">(</span><span class="w">
</span><span class="p">[</span><span class="n">Parameter</span><span class="p">()]</span><span class="w">
</span><span class="p">[</span><span class="n">System.String</span><span class="p">[]]</span><span class="w">
</span><span class="nv">$NodeName</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'localhost'</span><span class="w">
</span><span class="p">)</span><span class="w">
</span><span class="n">Import-DscResource</span><span class="w"> </span><span class="nt">-Module</span><span class="w"> </span><span class="nx">xRemoteDesktopAdmin</span><span class="w">
</span><span class="n">Import-DSCResource</span><span class="w"> </span><span class="nt">-ModuleName</span><span class="w"> </span><span class="nx">StorageDsc</span><span class="w">
</span><span class="n">Import-DSCResource</span><span class="w"> </span><span class="nt">-ModuleName</span><span class="w"> </span><span class="nx">xPendingReboot</span><span class="w">
</span><span class="n">Node</span><span class="w"> </span><span class="nv">$NodeName</span><span class="w">
</span><span class="p">{</span><span class="w">
</span><span class="n">LocalConfigurationManager</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">RebootNodeIfNeeded</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="bp">$true</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="c">#region RDP</span><span class="w">
</span><span class="n">xRemoteDesktopAdmin</span><span class="w"> </span><span class="nx">RemoteDesktopSettings</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">Ensure</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'Present'</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="c">#endregion</span><span class="w">
</span><span class="n">xPendingReboot</span><span class="w"> </span><span class="nx">Reboot1</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">Name</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'BeforeManageDisk'</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="c">#region Disk</span><span class="w">
</span><span class="kr">if</span><span class="w"> </span><span class="p">(</span><span class="n">Get-CimInstance</span><span class="w"> </span><span class="nt">-ClassName</span><span class="w"> </span><span class="nx">Win32_CDROMDrive</span><span class="p">)</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">OpticalDiskDriveLetter</span><span class="w"> </span><span class="nx">SetFirstOpticalDiskDriveLetterToZ</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">DiskId</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">1</span><span class="w">
</span><span class="n">DriveLetter</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'Z'</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="n">WaitForDisk</span><span class="w"> </span><span class="nx">Disk2</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">DiskId</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s2">"2"</span><span class="w">
</span><span class="n">RetryIntervalSec</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">10</span><span class="w">
</span><span class="n">RetryCount</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="mi">3</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="n">Disk</span><span class="w"> </span><span class="nx">EVolume</span><span class="w"> </span><span class="p">{</span><span class="w">
</span><span class="n">DiskId</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s2">"2"</span><span class="w">
</span><span class="n">DriveLetter</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'E'</span><span class="w">
</span><span class="n">FSLabel</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'Data'</span><span class="w">
</span><span class="n">DependsOn</span><span class="w"> </span><span class="o">=</span><span class="w"> </span><span class="s1">'[WaitForDisk]Disk2'</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="c">#endregion</span><span class="w">
</span><span class="p">}</span><span class="w">
</span><span class="p">}</span></code></pre>
</div>
</div>
<div class="paragraph">
<p>Once the configuration written, you must:</p>
</div>
<div class="olist arabic">
<ol class="arabic">
<li>
<p>Prepare a package</p>
</li>
<li>
<p>Publish the package</p>
</li>
</ol>
</div>
<div class="sect2">
<h3 id="preparation_of_the_package"><a class="anchor" href="#preparation_of_the_package"></a><a class="link" href="#preparation_of_the_package">Preparation of the package</a></h3>
<div class="paragraph">
<p>You must install all dependencies/modules on your computer.
In my case:</p>
</div>
<div class="listingblock">