RCFMARTIN

PWSH

PS\> ~/Visitor: $⠀ Get-RcfMartin

Name : Ricardo Martin

Roles : [ "DevOps", "DevSecOps", "Cybersecurity" ]

Focus : [ "Automation", "Security", "Scripting" ]

PowershellEnthusiast : True

LinuxEnthusiast : True

GymRat : True

CaffeineAddicted : True

PS\> ~/Visitor: $⠀ █

# Quick navigation

Get-Blog Technical posts on automation, DevSecOps & scripting → Get-Portfolio Skills, technical stack and contact information → Get-PSRepository Currently published powershell modules ↗

⎇ main

a3f92c1 fix: it worked on my machine so shipping it rcfmartin 12 min ago │b81d4e7 fix: ping worked so the network is fine (it was not fine) rcfmartin 1 hour ago │c55a012 chore: opened ticket, fixed issue, closed ticket, ticket reopened by user rcfmartin 2 hours ago │d29f38b fix: user said it is broken, computer was off rcfmartin 4 hours ago │g90e153 fix: works now, no idea why, not asking questions rcfmartin yesterday │h13d76a fix: rm -rf executed on wrong server, updated resume just in case rcfmartin yesterday │k92b310 docs: wrote a comment that explains absolutely nothing rcfmartin 2 days ago │l58e204 fix: packet loss resolved by aggressively blaming the cable rcfmartin 3 days ago │m71a983 fix: DNS. it is always DNS. it was DNS rcfmartin 3 days ago │r65a123 chore: ran the same command twice expecting different results rcfmartin 5 days ago │y89e231 fix: googled the same regex for the fifth time this month rcfmartin 2 weeks ago │z03f567 chore: reboot fixed it, root cause is the mystery of the universe rcfmartin 2 weeks ago │dd2e789 docs: added do not touch comment, touched it the next day rcfmartin 3 weeks ago │ez1e084 chore: spent 3 hours automating a 5 minute task, no regrets rcfmartin 3 weeks ago │a3f92c1 fix: it worked on my machine so shipping it rcfmartin 12 min ago │b81d4e7 fix: ping worked so the network is fine (it was not fine) rcfmartin 1 hour ago │c55a012 chore: opened ticket, fixed issue, closed ticket, ticket reopened by user rcfmartin 2 hours ago │d29f38b fix: user said it is broken, computer was off rcfmartin 4 hours ago │g90e153 fix: works now, no idea why, not asking questions rcfmartin yesterday │h13d76a fix: rm -rf executed on wrong server, updated resume just in case rcfmartin yesterday │k92b310 docs: wrote a comment that explains absolutely nothing rcfmartin 2 days ago │l58e204 fix: packet loss resolved by aggressively blaming the cable rcfmartin 3 days ago │m71a983 fix: DNS. it is always DNS. it was DNS rcfmartin 3 days ago │r65a123 chore: ran the same command twice expecting different results rcfmartin 5 days ago │y89e231 fix: googled the same regex for the fifth time this month rcfmartin 2 weeks ago │z03f567 chore: reboot fixed it, root cause is the mystery of the universe rcfmartin 2 weeks ago │dd2e789 docs: added do not touch comment, touched it the next day rcfmartin 3 weeks ago │ez1e084 chore: spent 3 hours automating a 5 minute task, no regrets rcfmartin 3 weeks ago │

PS > Get-LatestPosts⠀ -Count⠀ 3⠀

View all →

Powershell 15 min read

Parallel and Bulk REST Patterns in PowerShell

Sequential `Invoke-RestMethod` calls in a foreach loop are the slow path. This post covers the parallel patterns that actually work `ForEach-Object -Parallel` with per-branch sessions, runspace pools for finer control, provider-native batching, client-side token buckets so you throttle yourself before the API does, and shared cancellation so Ctrl+C stops every branch cleanly.

Powershell 16 min read

REST Authentication Patterns Beyond Bearer Tokens

Client credentials is the tutorial example. Real APIs want authorization-code with PKCE for interactive users, device code for headless CLIs, JWT client assertions for keyless federation, HMAC-signed requests for AWS-style access, mTLS for zero-trust, and managed identity when the platform gives you one. This post implements each pattern in PowerShell with the same begin/process/end + try/catch discipline as the rest of the series.

Powershell 15 min read

Resilient REST API Calls in PowerShell

A naked Invoke-RestMethod is one 429 or one transient TCP reset away from breaking your pipeline. This post builds a proper resilient REST client in PowerShell exponential backoff with jitter, Retry-After honouring, pagination handling, idempotency keys for retryable writes, and TLS pinning without ever disabling verification.