Blue-green deployment variables

Geert_Massa · 1 August 2018 07:55

Hello.
We now fully take down our full application and install everything.
We are thinking to switching to a blue-green deployment to limit the downtime.
Now there is 1 environment, called production.
So this has to be split up in a blue and a green environment.
But I have hundreds of variables linked to this Production environment.
What is the best way to migrate them to support a blue green deployment?

reece.walsh · 2 August 2018 03:22

Hi Geert,

Thanks for getting in touch,

Thanks for getting in touch! While there’s no way to duplicate mass variables in the UI (you can only duplicate single variables), this is possible for you to do via the API with a custom script. We have a few examples that accomplish similar things around duplicating variables which I hope help you out.

The following script will create multiple environment-scoped variables at once.

github.com

OctopusDeploy/OctopusDeploy-Api/blob/master/REST/PowerShell/Variables/CreateEnvironmentScopedVariables.ps1

$baseUri = "http://output.url"           # the address of your octopus server

$apiKey = "API-APIKEYAPIKEYAPIKEY"           # an api-key from an account with permissions to create
                                             # variables on the environment you specify

$projectName = "Project Name" # If you don't know your project Id add your project name here
                              # and the script will print out your project Id on the first run,
                              # then you can add it below

$projectId = ""               # set this if you know it, the script will run faster if it has
                              # a projectId, otherwise it will look up the project using its name

$environment = "Production"   # the name of the environment you want to scope the variables to

$variablesToAdd = "First", "Second", "Third"  #all the variables you want to createe

function Get-OctopusResource([string]$uri) {
    Write-Host "[GET]: $uri"
    return Invoke-RestMethod -Method Get -Uri "$baseUri/$uri" -Headers $headers
}

This file has been truncated. show original

This script will migrate variables from a variable set to a specified project.

github.com

OctopusDeploy/OctopusDeploy-Api/blob/master/REST/PowerShell/Variables/MigrateVariableSetVariablesToProject.ps1

$baseUri = "http://octopus.url" # <-- Update this to the base URL to your Octopus server(i.e. not including 'app' or 'api'
$apiKey = "API-xxxxxxxxxxxxxxxxxxxxxxxxxx" # <-- Update this to your API key
$headers = @{"X-Octopus-ApiKey" = $apiKey}
$libraryVariableSetId = "LibraryVariableSets-1" # <-- Update this to the Id of your variable set
$projectName = "ProejctName" # <-- Update this to the name of your project

function Get-OctopusResource([string]$uri) {
    Write-Host "[GET]: $uri"
    return Invoke-RestMethod -Method Get -Uri "$baseUri/$uri" -Headers $headers
}

function Put-OctopusResource([string]$uri, [object]$resource) {
    Write-Host "[PUT]: $uri"
    #Write-Output $resource | ConvertTo-Json -Depth 10
    Invoke-RestMethod -Method Put -Uri "$baseUri/$uri" -Body $($resource | ConvertTo-Json -Depth 10) -Headers $headers
}

$libVarSet = Get-OctopusResource "api/libraryvariablesets/$libraryVariableSetId"
#Write-Output $libVarSet | ConvertTo-Json -Depth 10
$varSet = Get-OctopusResource "api/variables/$($libVarSet.VariableSetId)"

This file has been truncated. show original

I hope this helps!

If you require any further assistance or clarification, please let me know

Kind Regards,

Reece

system · 1 September 2018 03:22

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.