Skip to main content

PowerShell GET/POST to Bitbucket API

I guarantee there is a better way to do this, but it took me a while to find the powershell syntax to do GET/POSTing, so hopefully this helps save someone some time.  And yeah, I'm aware that it's saving the password variable in plaintext.  Something to consider for v2.

The idea behind this (partial) script is that you can get most of the pre-setup done automatically.  One of the issues I haven't resolved yet is automatically accepting the ssh prompts (tried pre-injecting stuff, bunch of other things, no luck).  Not a huge deal since the biggest issue is the POSTing of the ssh key to Bitbucket.

This is a small piece of a project to automagically set up a dev workstation from a bare machine.  I think I'll try to post all of the code up when it's done - seems to be a common issue.

Also, I am really starting to get annoyed w. Blogger's inability to do code snippets.  One of these days I'll fix it...or move to Github gists for everything...
<#
    initDevEnviro.ps1
    User input required is bitbucket user/pass
#>
function Pause {Read-Host 'Press Enter to continue...' | Out-Null}
& {
 $wid=[System.Security.Principal.WindowsIdentity]::GetCurrent()
 $prp=new-object System.Security.Principal.WindowsPrincipal($wid)
 $adm=[System.Security.Principal.WindowsBuiltInRole]::Administrator
 $IsAdmin=$prp.IsInRole($adm)
 if ($IsAdmin)
 {
  Write-Host "Script is being executed as admin, proceeding..." -ForegroundColor Green
 }
 else {
    Write-Host "Please re-run the script as an admin." -ForegroundColor Red
    pause
    Exit 1
 }
}
$rootPath = "$env:USERPROFILE\git\projectPath" # This should model the repo structure, plus all IIS config below relies on it.
Write-Host "This is a new workstation (right?), so the user sshkey needs to be generated" -ForegroundColor Cyan
if (!(Test-Path "$env:USERPROFILE\.ssh")) {
    New-Item -ItemType directory "$env:USERPROFILE\.ssh"
}
$PkeyFile = "$env:USERPROFILE\.ssh\id_rsa"
if (!(Test-Path $PkeyFile)) {
    Try {
        Write-Host "No $PkeyFile found, generating one for you..." -ForegroundColor Cyan
        [string]$command = "C:\tools\cmder\vendor\msysgit\bin\ssh-keygen.exe"
        [array]$arguments = "-f", "$pkeyFile", "-t", "rsa", "-N", "''"
        & $command $arguments;
    }
    Catch {
        Write-Host "Generating the SSH key failed!"
        Write-Host $_.Exception.Message -ForegroundColor Red
    }
}
else {
    Write-Host "Looks like you already have an SSH key, skipping the generation process!" -ForegroundColor Green
}
Write-Host "Setting some key variables..."
$keyFile = "$env:USERPROFILE\.ssh\id_rsa.pub"
$key = Get-Content $keyFile -Raw
   
Write-Host "PROMPT: ensure the user has been added to our bitbucket account before continuing `r
 Now we need to connect to bitbucket and install the new ssh key" -ForegroundColor Cyan
 Pause
$cred = Get-Credential -Message "Enter your BitBucket credentials"
[string]$userName = $cred.GetNetworkCredential().username # Save the username as a variable
[string]$password = $cred.GetNetworkCredential().password # Save the password as a variable
$uri = "https://api.bitbucket.org/1.0/users/$userName/ssh-keys"
[string]$label = hostname
$postData = @{
    key = "$key" #get id-rsa key here
    label = "$label" #just a label, can be anything
}
Write-Host "Now we actually connect to the Bitbucket REST API" -ForegroundColor Cyan
Try {
    Write-Host "Is there already a key in Bitbucket?" -ForegroundColor Cyan
    Try {
        $params = @{
            Uri = $uri;
            Method = 'GET';
            Headers = @{
            Authorization = 'Basic ' + [Convert]::ToBase64String(
                [Text.Encoding]::ASCII.GetBytes("$($userName):$($password)"));
            }
            ContentType = 'application/json';
        }
        $APIcallResults = Invoke-RestMethod @params
        $returnedLabel = $APIcallResults.label
        $labelMatch = $returnedLabel -match $label
    }
    Catch {
        Write-Host "GETing from the Bitbucket API failed!"
        Write-Host $_.Exception.Message -ForegroundColor Red
    }
    if ($returnedLabel | Where-Object {$_ -eq $label}) {
        Write-Host "Key already exists in Bitbucket, skipping..." -ForegroundColor Green
    }
    else {
        Write-Host "Key doesn't exist in Bitbucket, adding..." -ForegroundColor Cyan
        Write-Host "Doing the POST..."
        $params = @{
            Uri = $uri;
            Method = 'POST';
            Headers = @{
            Authorization = 'Basic ' + [Convert]::ToBase64String(
                [Text.Encoding]::ASCII.GetBytes("$($userName):$($password)"));
            }
            ContentType = 'application/json';
            Body = (ConvertTo-Json $postData -Compress)
        }
        Invoke-RestMethod @params
        Write-Host "Let's test to ensure the key was stored correctly..." -ForegroundColor Cyan
        Try {
            $params = @{
                Uri = $uri;
                Method = 'GET';
                Headers = @{
                Authorization = 'Basic ' + [Convert]::ToBase64String(
                    [Text.Encoding]::ASCII.GetBytes("$($userName):$($password)"));
                }
                ContentType = 'application/json';
            }
            $APIcallResults = Invoke-RestMethod @params
            $returnedLabel = $APIcallResults.label
            if ($returnedLabel | Where-Object {$_ -eq $label}) {
                Write-Host "Bling! Key successfully imported to Bitbucket!" -ForegroundColor Green
            }
            else {
                Write-Host "Ruh roh Shaggy, key import broke - the key hasn't been added!"
                Pause
                Exit 1
            }
        }
        Catch {
            Write-Host "GETing from the Bitbucket API failed!"
            Write-Host $_.Exception.Message -ForegroundColor Red
        }
    }
}
Catch {
    Write-Host "Connecting to the Bitbucket API failed!"
    Write-Host $_.Exception.Message -ForegroundColor Red
}

Comments

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:


You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…