{"id":343,"date":"2025-06-23T12:44:30","date_gmt":"2025-06-23T12:44:30","guid":{"rendered":"http:\/\/sreschool.com\/blog\/?p=343"},"modified":"2025-06-23T12:44:32","modified_gmt":"2025-06-23T12:44:32","slug":"%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/","title":{"rendered":"\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial"},"content":{"rendered":"\n

1. Introduction & Overview<\/h1>\n\n\n\n

What is Runbooks as Code<\/strong>?<\/h3>\n\n\n\n

Runbooks as Code (RaC) refers to the practice of writing operational procedures and incident response steps in code<\/strong>, typically using Infrastructure as Code (IaC)<\/strong> and automation frameworks<\/strong> (like Ansible, Python scripts, Terraform, etc.), which can be version-controlled, tested, reviewed, and executed<\/strong> automatically or semi-automatically.<\/p>\n\n\n\n

\n

\ud83e\udde0 Think of RaC as the codified version of a traditional playbook<\/strong>, enabling automated incident recovery, audits, and compliance workflows.<\/p>\n<\/blockquote>\n\n\n\n

History or Background<\/h3>\n\n\n\n
    \n
  • Originally, runbooks<\/em> were manual documents<\/strong> created by sysadmins for common operational procedures.<\/li>\n\n\n\n
  • With the rise of DevOps & SRE<\/strong>, there was a push to automate everything<\/strong> \u2014 leading to “Runbooks as Code.”<\/strong><\/li>\n\n\n\n
  • The concept borrows from IaC<\/strong> principles and became popular with tools like Ansible, Rundeck, StackStorm, and GitOps workflows<\/strong>.<\/li>\n<\/ul>\n\n\n\n

    Why is it Relevant in DevSecOps?<\/h3>\n\n\n\n

    Runbooks as Code support continuous security and compliance<\/strong> by:<\/p>\n\n\n\n

      \n
    • Automating incident response securely.<\/li>\n\n\n\n
    • Reducing human error<\/strong> in security events.<\/li>\n\n\n\n
    • Enforcing auditable, version-controlled<\/strong> SOPs.<\/li>\n\n\n\n
    • Integrating with SIEM\/SOAR, CI\/CD<\/strong>, and cloud security<\/strong> tools.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n

      2. Core Concepts & Terminology<\/h2>\n\n\n\n

      Key Terms & Definitions<\/h3>\n\n\n\n
      Term<\/th>Definition<\/th><\/tr><\/thead>
      Runbook<\/strong><\/td>A documented set of instructions for routine or emergency IT tasks.<\/td><\/tr>
      IaC<\/strong><\/td>Infrastructure as Code \u2014 managing infrastructure through machine-readable definition files.<\/td><\/tr>
      SOAR<\/strong><\/td>Security Orchestration, Automation, and Response \u2014 tools that automate security operations.<\/td><\/tr>
      GitOps<\/strong><\/td>Git-based approach to infrastructure and application management.<\/td><\/tr>
      Immutable Infrastructure<\/strong><\/td>Infrastructure that is not changed after deployment, often rebuilt completely on updates.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      How It Fits into the DevSecOps Lifecycle<\/h3>\n\n\n\n
      graph TD\nDev --> DevSecOps\nDevSecOps --> SecureCI[\"Secure CI\/CD\"]\nSecureCI --> RunbookAsCode[\"Runbooks as Code\"]\nRunbookAsCode --> Automation[\"Automated Security Response\"]\nAutomation --> Monitoring[\"Continuous Monitoring\"]\nMonitoring --> Feedback\nFeedback --> Dev\n<\/code><\/pre>\n\n\n\n
        \n
      • Shift-left security<\/strong>: Automate security early in pipelines.<\/li>\n\n\n\n
      • Auto-remediation<\/strong>: Handle misconfigs or threats with RaC.<\/li>\n\n\n\n
      • Auditability<\/strong>: Every step logged in code and version-controlled.<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        3. Architecture & How It Works<\/h2>\n\n\n\n
        Components<\/h3>\n\n\n\n
          \n
        • Source Code Repository<\/strong> (e.g., GitHub)<\/li>\n\n\n\n
        • Automation Engine<\/strong> (e.g., Ansible, Puppet, SaltStack, etc.)<\/li>\n\n\n\n
        • CI\/CD Tool<\/strong> (e.g., Jenkins, GitLab, Azure DevOps)<\/li>\n\n\n\n
        • Alerting\/Triggering Tool<\/strong> (e.g., PagerDuty, Prometheus, CloudWatch)<\/li>\n\n\n\n
        • SOAR or Orchestration Layer<\/strong> (e.g., StackStorm, Rundeck)<\/li>\n<\/ul>\n\n\n\n
          Internal Workflow (Step-by-Step)<\/h3>\n\n\n\n
            \n
          1. Trigger<\/strong>: Incident alert from monitoring tool (e.g., Prometheus)<\/li>\n\n\n\n
          2. Lookup<\/strong>: Corresponding Runbook as Code triggered from Git<\/li>\n\n\n\n
          3. Execution<\/strong>: Automation engine runs predefined scripts (e.g., block IP, restart pod)<\/li>\n\n\n\n
          4. Feedback<\/strong>: Logs pushed to observability tool (ELK, Grafana)<\/li>\n\n\n\n
          5. Audit<\/strong>: Git history and logs serve compliance<\/li>\n<\/ol>\n\n\n\n
            Architecture Diagram (Descriptive)<\/h3>\n\n\n\n
            +-----------+       +---------+       +--------------+       +-------------+\n| Monitoring| ----> | CI\/CD   | ----> | Automation   | ----> | Cloud Infra |\n| Tool      |       | Tool    |       | Engine (RaC) |       | (AWS, Azure)|\n+-----------+       +---------+       +--------------+       +-------------+\n        |                  |                  |                      |\n        v                  v                  v                      v\n    Alert Trigger     Version Control      Playbook Run         Secure State\n<\/code><\/pre>\n\n\n\n
            Integration Points with CI\/CD or Cloud<\/h3>\n\n\n\n
            Tool Type<\/th>Examples<\/th>Integration Approach<\/th><\/tr><\/thead>
            CI\/CD Tools<\/td>GitHub Actions, GitLab CI<\/td>Trigger RaC scripts post-deploy<\/td><\/tr>
            Cloud Providers<\/td>AWS Lambda, Azure Functions<\/td>Auto-trigger remediation from cloud logs<\/td><\/tr>
            Security Tools<\/td>CrowdStrike, Wazuh, OSSEC<\/td>Link alerts to RaC playbooks via webhook<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
            \n\n\n\n
            4. Installation & Getting Started<\/h2>\n\n\n\n
            Prerequisites<\/h3>\n\n\n\n
              \n
            • Git installed and GitHub account<\/li>\n\n\n\n
            • Docker (optional)<\/li>\n\n\n\n
            • Python or Ansible installed<\/li>\n\n\n\n
            • Any cloud account (AWS\/GCP)<\/li>\n\n\n\n
            • Basic DevOps\/CI pipeline (Jenkins\/GitLab)<\/li>\n<\/ul>\n\n\n\n
              Hands-On Guide: Setup a Basic Runbook as Code<\/h3>\n\n\n\n
              Objective:<\/strong> Automatically restart a failed NGINX service using Ansible when a server health check fails.<\/p>\n\n\n\n
              Step 1: Install Ansible<\/h4>\n\n\n\n
              sudo apt update\nsudo apt install ansible\n<\/code><\/pre>\n\n\n\n
              Step 2: Create the Runbook<\/h4>\n\n\n\n
              File: restart-nginx.yml<\/code><\/strong><\/p>\n\n\n\n
              ---\n- name: Restart NGINX when down\n  hosts: webservers\n  become: yes\n  tasks:\n    - name: Ensure NGINX is running\n      service:\n        name: nginx\n        state: restarted\n<\/code><\/pre>\n\n\n\n
              Step 3: Set Up Inventory<\/h4>\n\n\n\n
              File: hosts<\/code><\/strong><\/p>\n\n\n\n
              [webservers]\n192.168.1.20 ansible_user=ubuntu ansible_ssh_private_key_file=~\/.ssh\/id_rsa\n<\/code><\/pre>\n\n\n\n
              Step 4: Execute Manually (Simulate alert)<\/h4>\n\n\n\n
              ansible-playbook -i hosts restart-nginx.yml\n<\/code><\/pre>\n\n\n\n
              Step 5: Automate with GitHub Actions<\/h4>\n\n\n\n
              File: .github\/workflows\/restart-nginx.yml<\/code><\/strong><\/p>\n\n\n\n
              name: Restart NGINX on Alert\non:\n  push:\n    paths:\n      - restart-nginx.yml\njobs:\n  runbook:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\/checkout@v2\n      - name: Run Ansible Playbook\n        run: ansible-playbook -i hosts restart-nginx.yml\n<\/code><\/pre>\n\n\n\n
              \n\n\n\n
              5. Real-World Use Cases<\/h2>\n\n\n\n
              \u2705 Use Case 1: Auto-Patch Vulnerabilities<\/h3>\n\n\n\n
                \n
              • Vulnerability scanner (e.g., Nessus) finds a flaw.<\/li>\n\n\n\n
              • RaC patches systems via automation scripts.<\/li>\n<\/ul>\n\n\n\n
                \u2705 Use Case 2: Auto-Recover Cloud Resource<\/h3>\n\n\n\n
                  \n
                • AWS CloudWatch detects failed EC2.<\/li>\n\n\n\n
                • Lambda triggers RaC to redeploy infrastructure via Terraform.<\/li>\n<\/ul>\n\n\n\n
                  \u2705 Use Case 3: Rotate Credentials Automatically<\/h3>\n\n\n\n
                    \n
                  • Secrets manager triggers RaC when keys expire.<\/li>\n\n\n\n
                  • Rotation logic runs and updates secrets across services.<\/li>\n<\/ul>\n\n\n\n
                    \u2705 Use Case 4: Security Misconfiguration Fix<\/h3>\n\n\n\n
                      \n
                    • Kubernetes misconfigured pod detected by OPA.<\/li>\n\n\n\n
                    • RaC re-applies secure deployment YAML via kubectl<\/code>.<\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n
                      6. Benefits & Limitations<\/h2>\n\n\n\n
                      \u2705 Key Benefits<\/h3>\n\n\n\n
                        \n
                      • \ud83d\udd04 Automation<\/strong> of repetitive and sensitive ops<\/li>\n\n\n\n
                      • \ud83d\udd0d Audit trails<\/strong> for compliance<\/li>\n\n\n\n
                      • \ud83d\udca5 Faster MTTR (Mean Time To Recovery)<\/strong><\/li>\n\n\n\n
                      • \ud83e\udd1d Team Collaboration<\/strong> via version control<\/li>\n<\/ul>\n\n\n\n
                        \u274c Common Challenges<\/h3>\n\n\n\n
                        Challenge<\/th>Mitigation<\/th><\/tr><\/thead>
                        Complexity of scripting<\/td>Use templated modules and community libs<\/td><\/tr>
                        Security of scripts<\/td>Use secrets manager and RBAC<\/td><\/tr>
                        Version sprawl<\/td>GitOps enforcement<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                        \n\n\n\n
                        7. Best Practices & Recommendations<\/h2>\n\n\n\n
                        \ud83d\udd10 Security & Compliance<\/h3>\n\n\n\n
                          \n
                        • Use IAM roles<\/strong>, not hardcoded creds.<\/li>\n\n\n\n
                        • Enable logging & audit trails<\/strong> for all executions.<\/li>\n\n\n\n
                        • Integrate with compliance scanners<\/strong> (e.g., Chef InSpec).<\/li>\n<\/ul>\n\n\n\n
                          \u2699\ufe0f Maintenance & Performance<\/h3>\n\n\n\n
                            \n
                          • Write idempotent<\/strong> playbooks.<\/li>\n\n\n\n
                          • Use linter tools<\/strong> like ansible-lint<\/code>, yamllint<\/code>.<\/li>\n\n\n\n
                          • Document clearly using markdown or README<\/strong> in each repo.<\/li>\n<\/ul>\n\n\n\n
                            \ud83d\udca1 Automation Ideas<\/h3>\n\n\n\n
                              \n
                            • Auto-scale based on performance<\/li>\n\n\n\n
                            • Auto-disable compromised accounts<\/li>\n\n\n\n
                            • Integrate with GitOps (ArgoCD) for declarative management<\/li>\n<\/ul>\n\n\n\n
                              \n\n\n\n
                              8. Comparison with Alternatives<\/h2>\n\n\n\n
                              Feature<\/th>Manual Runbooks<\/th>Runbooks as Code<\/th>SOAR Platforms<\/th><\/tr><\/thead>
                              Version Controlled<\/td>\u274c<\/td>\u2705<\/td>\u2705<\/td><\/tr>
                              Reusable<\/td>\u274c<\/td>\u2705<\/td>\u2705<\/td><\/tr>
                              Security-Aware<\/td>\u274c<\/td>\u2705<\/td>\u2705<\/td><\/tr>
                              Expensive Licensing<\/td>\u274c<\/td>\u274c<\/td>\u2705 (Often)<\/td><\/tr>
                              Cloud-Native Integration<\/td>\u274c<\/td>\u2705<\/td>\u2705<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                              \n
                              \u2705 Choose RaC<\/strong> when:<\/p>\n\n\n\n
                                \n
                              • You want GitOps integration<\/li>\n\n\n\n
                              • You need reproducibility, auditability, and low cost<\/li>\n<\/ul>\n<\/blockquote>\n\n\n\n
                                \n\n\n\n
                                9. Conclusion<\/h2>\n\n\n\n
                                Runbooks as Code<\/strong> bring automation, reliability, and security to modern DevSecOps practices. By treating operational procedures as version-controlled code, teams can scale, secure, and audit their systems efficiently.<\/p>\n\n\n\n
                                \n
                                As DevSecOps matures, RaC will be a foundational building block<\/strong>, especially in regulated industries like finance, healthcare, and defense.<\/p>\n<\/blockquote>\n\n\n\n
                                \n\n\n\n
                                <\/p>\n","protected":false},"excerpt":{"rendered":"
                                1. Introduction & Overview What is Runbooks as Code? Runbooks as Code (RaC) refers to the practice of writing operational […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-343","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\n\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial - SRE School<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sreschool.com\/blog\/\ud83d\udcd8-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial - SRE School\" \/>\n<meta property=\"og:description\" content=\"1. Introduction & Overview What is Runbooks as Code? Runbooks as Code (RaC) refers to the practice of writing operational […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/\ud83d\udcd8-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2025-06-23T12:44:30+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-23T12:44:32+00:00\" \/>\n<meta name=\"author\" content=\"priteshgeek\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"priteshgeek\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/\",\"url\":\"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/\",\"name\":\"\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial - SRE School\",\"isPartOf\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#website\"},\"datePublished\":\"2025-06-23T12:44:30+00:00\",\"dateModified\":\"2025-06-23T12:44:32+00:00\",\"author\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db\"},\"breadcrumb\":{\"@id\":\"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sreschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/sreschool.com\/blog\/#website\",\"url\":\"https:\/\/sreschool.com\/blog\/\",\"name\":\"SRESchool\",\"description\":\"Master SRE. Build Resilient Systems. Lead the Future of Reliability\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/sreschool.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db\",\"name\":\"priteshgeek\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g\",\"caption\":\"priteshgeek\"},\"url\":\"https:\/\/sreschool.com\/blog\/author\/priteshgeek\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial - SRE School","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/sreschool.com\/blog\/\ud83d\udcd8-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/","og_locale":"en_US","og_type":"article","og_title":"\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial - SRE School","og_description":"1. Introduction & Overview What is Runbooks as Code? Runbooks as Code (RaC) refers to the practice of writing operational […]","og_url":"https:\/\/sreschool.com\/blog\/\ud83d\udcd8-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/","og_site_name":"SRE School","article_published_time":"2025-06-23T12:44:30+00:00","article_modified_time":"2025-06-23T12:44:32+00:00","author":"priteshgeek","twitter_card":"summary_large_image","twitter_misc":{"Written by":"priteshgeek","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/","url":"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/","name":"\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2025-06-23T12:44:30+00:00","dateModified":"2025-06-23T12:44:32+00:00","author":{"@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db"},"breadcrumb":{"@id":"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/%f0%9f%93%98-runbooks-as-code-in-devsecops-an-in-depth-tutorial\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"\ud83d\udcd8 Runbooks as Code in DevSecOps: An In-Depth Tutorial"}]},{"@type":"WebSite","@id":"https:\/\/sreschool.com\/blog\/#website","url":"https:\/\/sreschool.com\/blog\/","name":"SRESchool","description":"Master SRE. Build Resilient Systems. Lead the Future of Reliability","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sreschool.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Person","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/6a53e3870889dd6a65b2e04b7bc3d7db","name":"priteshgeek","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/231a0e8b7a02636f2fbacf8dcf4494cb1cc0d49ecc9a8165fbaeaeeaf102641a?s=96&d=mm&r=g","caption":"priteshgeek"},"url":"https:\/\/sreschool.com\/blog\/author\/priteshgeek\/"}]}},"_links":{"self":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/343","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/comments?post=343"}],"version-history":[{"count":1,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/343\/revisions"}],"predecessor-version":[{"id":344,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/343\/revisions\/344"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=343"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=343"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=343"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}