-
Notifications
You must be signed in to change notification settings - Fork 111
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
Deprecate AzureRM - PowerShellContext #1394
base: main
Are you sure you want to change the base?
Conversation
1de47c9
to
637ce00
Compare
@@ -11,6 +11,9 @@ $OctopusAzureEnvironment = $OctopusParameters["Octopus.Action.Azure.Environment" | |||
$OctopusOpenIdJwt = $OctopusParameters["Octopus.OpenIdConnect.Jwt"] | |||
$OctopusUseOidc = ![string]::IsNullOrEmpty($OctopusOpenIdJwt) | |||
|
|||
## The script is passed the following parameters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which version of Server are you targeting? I've made a breaking change in Calamari (#1405) so you'll need to target a 28.x.x branch if this is going to 2024.4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'll need to be 2025.1 - so main is fine (i.e. I don't really want to push this out to on-prem).
Aside from that - the feature toggle should probably be flipped to prevent the usage of AzureRM by default (but with an escape hatch).
The AzureRM deprecation flag is required to be included in the AzurePowershellContext.ps1 to show a warning if users
are still using AzureRM module (Rather than Azure CLI).
This feature flag means users are presented with a warning atm - which will become an error at some point in the future.
The script update matches that performed in the prior AzureContext.ps1
[sc-74652]