-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do you update powershell module here #474
Comments
Use the PowerShell module from the gallery (EnterprisePolicyAsCode) - it is updated when releases are made via this GitHub repo |
@anwather sorry for taking time to come back...Is this what's already been used here - https://github.com/Azure/enterprise-azure-policy-as-code/tree/main/Module ? |
@chanakanissanka For instance - most of my projects only contain a single folder for Definitions - I use the PowerShell module to then run the commands to build and deploy policy and roles. |
@anwather Thanks for this clear instructions and that makes sense. |
@anwather I have no option but to fork the repo due to some bs regulations. Would it be possible to get an idea of the best way to accommodate future releases other than copying and pasting those scripts? Sorry if I'm asking something obvious. |
There is a script called Sync-Repo.ps1 in the repository which can do the copy.
The PowerShell module has been created to accommodate future release.
…________________________________
From: chanakanissanka ***@***.***>
Sent: Tuesday, 20 February 2024 10:36 AM
To: Azure/enterprise-azure-policy-as-code ***@***.***>
Cc: Mention ***@***.***>; Comment ***@***.***>; State change ***@***.***>; Subscribed ***@***.***>
Subject: Re: [Azure/enterprise-azure-policy-as-code] How do you update powershell module here (Issue #474)
@anwather<https://github.com/anwather> I have no option but to fork the repo due to some bs regulations. Would it be possible to get an idea of the best way to accommodate future releases other than copying and pasting those scripts? Sorry if I'm asking something obvious.
—
Reply to this email directly, view it on GitHub<#474 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACWCJVXSVFD6CQPN72PSGL3YUPOZTBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVEZTGNZRGYZDQMZYQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRSGEZTCMJQGM3DON5HORZGSZ3HMVZKMY3SMVQXIZI>.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hi Folks,
We intend to use this EPAC for our Azure Governance initiative, and one thing that came up during the evaluation was how best to stay up-to-date with the releases here with our local copy. Apologies If I'm asking something obvious here, still we can't get our head around how releases can be automated.
regards,
Chanaka
The text was updated successfully, but these errors were encountered: