{"id":12036,"date":"2026-11-19T18:30:00","date_gmt":"2026-11-19T18:30:00","guid":{"rendered":"https:\/\/www.cotocus.com\/blog\/?p=12036"},"modified":"2026-11-19T18:30:00","modified_gmt":"2026-11-19T18:30:00","slug":"reuse-a-proven-deploy-script","status":"publish","type":"post","link":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/","title":{"rendered":"Turn a Deploy Script That Worked Into a Reusable Module"},"content":{"rendered":"<p>You have a deployment script that finally behaves. It survived a messy release, it handles the odd retry, and the team trusts it. Next month another service needs deploying and the temptation is to write a new script, because the old one is welded to the first project. This how-to shows, step by step, how to turn that working script into a reusable module you can drop into the next project with light changes instead of a rewrite.<\/p>\n<p>The method is deliberately plain. No new tools are required: a version-controlled repository, a text editor and an hour of focus will do. Where an example helps, it uses a containerised service shipped through a standard CI job, but the same steps suit Terraform modules, Ansible roles or shell scripts.<\/p>\n<h2>Step 1: Confirm the script is worth reusing<\/h2>\n<p>Not every script deserves promotion. Check three things before you invest the effort. It must have run successfully in production at least a few times. You should be able to explain, in two sentences, what it does. And a second project should plausibly need roughly the same behaviour. If any answer is no, leave it where it is and revisit when the pattern repeats.<\/p>\n<h2>Step 2: Freeze a known-good copy<\/h2>\n<p>Tag the current version of the script in version control, with a message such as &#8220;proven on first release&#8221;. This tag is your safety net. If your refactor goes wrong, you can always return to the exact file that worked. Resist the urge to improve anything before you freeze it; the whole point is to preserve what is already proven.<\/p>\n<h2>Step 3: List everything that is specific to the first project<\/h2>\n<p>Read the script slowly with a highlighter, literal or virtual. Mark every value that belongs to that one service: names, paths, ports, environment names, registry locations, notification targets. Write them into a short list. In most scripts, you will find between five and fifteen such values, and that list is the blueprint for your inputs.<\/p>\n<h2>Step 4: Turn those values into inputs with defaults<\/h2>\n<p>Replace each hard-coded value with a variable or parameter. Give every input a default that reflects the common case, and decide which inputs are required. Keep the number of inputs modest; a module with thirty options is as hard to use as no module at all. If you are unsure whether something should be an input, ask whether the second project will really need to change it. If not, leave it fixed.<\/p>\n<h2>Step 5: Leave the working logic alone<\/h2>\n<p>This is the discipline that separates a safe extraction from a risky rewrite. The retry handling, the order of operations, the health check, the rollback trigger: these are the hard-won parts. Move them intact. You may reformat or comment, but do not restructure them while you are also changing the inputs. Changing one thing at a time means that if something breaks, you know exactly why.<\/p>\n<h2>Step 6: Write a short README beside it<\/h2>\n<p>Four headings are enough: what it does, what inputs it takes, what it assumes (language runtime, permissions, platform versions) and what it deliberately does not do. Add a line stating where it was proven and when. When someone opens the folder in six months, this note saves them an afternoon of guessing.<\/p>\n<h2>Step 7: Prove it on the original project first<\/h2>\n<p>Before offering the module to anyone else, switch the original project to use it. Run the full pipeline in a safe environment. The behaviour should be identical to the frozen version. If it differs, the difference is a bug in your extraction; fix it now, while the context is fresh. Compare logs side by side if you need to.<\/p>\n<h2>Step 8: Try it on a second, low-risk project<\/h2>\n<p>Now pick a small, forgiving service and wire the module in with different inputs. This is the real test, because it exposes assumptions you did not know you had: a path that happened to exist, a permission granted to one account only. Expect to fix two or three small things. Each fix makes the module more general and more trustworthy.<\/p>\n<p>If your team works on model-serving or data workflows, similar reuse thinking is already common; the notes in <a href=\"https:\/\/www.cotocus.com\/blog\/mlops-roadmap-a-complete-guide-for-data-scientists-and-engineering-teams\/\">a complete roadmap written for data scientists and engineers who ship models<\/a> show how repeatable stages keep deployments predictable.<\/p>\n<h2>What the result looks like in practice<\/h2>\n<p>Suppose the original script deployed a small web service to a container platform. After extraction, the module takes six inputs: service name, image reference, environment, health-check path, replica count and a notification target. Its README says it expects a container registry login to be present and a deploy permission on the target environment. The first project calls it with its own values and behaves exactly as before. The second project, a background worker with no web port, passes a different health-check path and a replica count of one, and ships on its first attempt.<\/p>\n<p>The difference is not dramatic on any single day. The real gain is cumulative: the third, fourth and fifth services need an afternoon instead of a week, and when a rollback bug is fixed it is fixed for all of them together.<\/p>\n<h2>Step 9: Version it and tell people<\/h2>\n<p>Tag a first release, such as v1.0, and write a two-line changelog. Post a short note in the team channel with a link to the README and an example of the simplest usage. Ask one colleague to try it and watch where they hesitate; those hesitation points are your documentation gaps. Consumers should pin to a version so that updates arrive when they choose, not by surprise.<\/p>\n<h2>Step 10: Feed fixes back in<\/h2>\n<p>When a real incident reveals a missing check, add it to the module and release a new tag. Every project that upgrades benefits, and nobody needs to remember the lesson individually. This feedback loop is what makes reuse compound over time. If you want a sense of how faster, steadier releases show up in practice, <a href=\"https:\/\/www.cotocus.com\/blog\/how-mlops-drives-faster-machine-learning-deployments-and-business-growth\/\">an article on how MLOps speeds up model deployments<\/a> offers a useful picture.<\/p>\n<h2>A quick checklist to keep nearby<\/h2>\n<ul>\n<li>Tagged the proven original before touching it.<\/li>\n<li>Listed every project-specific value.<\/li>\n<li>Converted them to inputs with defaults, and kept the input count small.<\/li>\n<li>Left the retry, ordering and rollback logic untouched.<\/li>\n<li>Wrote a README with assumptions and limits.<\/li>\n<li>Verified identical behaviour on the original project.<\/li>\n<li>Tested on a second project and fixed what broke.<\/li>\n<li>Released a versioned tag and announced it.<\/li>\n<\/ul>\n<h2>Reviewing and securing the shared piece<\/h2>\n<p>A reusable deployment module touches many services, so changes deserve a careful second look. Ask a colleague to review every edit, run the sample project in CI on each change and keep credentials out of the module entirely. Pass secrets through your platform&#8217;s usual secure mechanism, and write down which permissions the module needs and no more. If something looks suspicious in a review, hold the release; a day&#8217;s delay is cheaper than a broken deploy across several services.<\/p>\n<h2>Mistakes to avoid<\/h2>\n<p>Over-generalising is the usual trap. If you try to make the module handle every future scenario, it becomes a maze of flags. Build for the two projects you know and widen only when a third demands it. Another trap is hidden coupling: a module that quietly reads an environment variable set only on one machine. List such dependencies in the README and fail early, with a clear message, if one is missing.<\/p>\n<p>Finally, avoid the &#8220;temporary fork&#8221;. A copy made for one urgent release tends to live forever. If a project truly needs a variation, add an input or open a change to the shared module instead.<\/p>\n<h2>A small note on finding good formats<\/h2>\n<p>Engineers who like to see how others organise repeatable formats sometimes browse outside the usual blogs. <a href=\"https:\/\/ranchiorbit.com\/\">RanchiOrbit<\/a> is an events website whose sections run from event pages and venue pages to a forum, a blog and stories, and the way such a site reuses one layout across many events is a neat everyday reminder of the principle.<\/p>\n<h2>Where this leaves you<\/h2>\n<p>After one pass through these steps you will own a small, tested module, a note explaining it and a habit: when something works, give it a home and a version. The next service gets deployed from the middle of the process, not the start. Keep the original tag, keep the README honest and keep improving the shared version, and the time you spend on this will come back many times over.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A step-by-step guide to extracting a proven deployment script into a versioned, documented module you can reuse on the next service with light changes.<\/p>\n","protected":false},"author":37,"featured_media":12037,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[147],"tags":[],"class_list":["post-12036","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Turn a Deploy Script That Worked Into a Reusable Module - Cotocus<\/title>\n<meta name=\"description\" content=\"Step by step: turn a proven deployment script into a reusable module with inputs, a README and versioning, and reuse it safely on your next service.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Turn a Deploy Script That Worked Into a Reusable Module - Cotocus\" \/>\n<meta property=\"og:description\" content=\"Step by step: turn a proven deployment script into a reusable module with inputs, a README and versioning, and reuse it safely on your next service.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/\" \/>\n<meta property=\"og:site_name\" content=\"Cotocus\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-19T18:30:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-769135-banner.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Nikhil Farooqui\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nikhil Farooqui\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/\"},\"author\":{\"name\":\"Nikhil Farooqui\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"headline\":\"Turn a Deploy Script That Worked Into a Reusable Module\",\"datePublished\":\"2026-11-19T18:30:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/\"},\"wordCount\":1414,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-769135-banner.png\",\"articleSection\":[\"DevOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/\",\"name\":\"Turn a Deploy Script That Worked Into a Reusable Module - Cotocus\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-769135-banner.png\",\"datePublished\":\"2026-11-19T18:30:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\"},\"description\":\"Step by step: turn a proven deployment script into a reusable module with inputs, a README and versioning, and reuse it safely on your next service.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-769135-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-769135-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/reuse-a-proven-deploy-script\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Turn a Deploy Script That Worked Into a Reusable Module\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/\",\"name\":\"Cotocus\",\"description\":\"Shaping Tomorrow\u2019s Tech Today\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/#\\\/schema\\\/person\\\/419007bef27e8d85890550d783b96c50\",\"name\":\"Nikhil Farooqui\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g\",\"caption\":\"Nikhil Farooqui\"},\"url\":\"https:\\\/\\\/www.cotocus.com\\\/blog\\\/author\\\/nikhil-farooqui\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Turn a Deploy Script That Worked Into a Reusable Module - Cotocus","description":"Step by step: turn a proven deployment script into a reusable module with inputs, a README and versioning, and reuse it safely on your next service.","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:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/","og_locale":"en_US","og_type":"article","og_title":"Turn a Deploy Script That Worked Into a Reusable Module - Cotocus","og_description":"Step by step: turn a proven deployment script into a reusable module with inputs, a README and versioning, and reuse it safely on your next service.","og_url":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/","og_site_name":"Cotocus","article_published_time":"2026-11-19T18:30:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-769135-banner.png","type":"image\/png"}],"author":"Nikhil Farooqui","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Nikhil Farooqui","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/#article","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/"},"author":{"name":"Nikhil Farooqui","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"headline":"Turn a Deploy Script That Worked Into a Reusable Module","datePublished":"2026-11-19T18:30:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/"},"wordCount":1414,"commentCount":0,"image":{"@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-769135-banner.png","articleSection":["DevOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/","url":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/","name":"Turn a Deploy Script That Worked Into a Reusable Module - Cotocus","isPartOf":{"@id":"https:\/\/www.cotocus.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/#primaryimage"},"image":{"@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/#primaryimage"},"thumbnailUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-769135-banner.png","datePublished":"2026-11-19T18:30:00+00:00","author":{"@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50"},"description":"Step by step: turn a proven deployment script into a reusable module with inputs, a README and versioning, and reuse it safely on your next service.","breadcrumb":{"@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/#primaryimage","url":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-769135-banner.png","contentUrl":"https:\/\/www.cotocus.com\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-769135-banner.png","width":1200,"height":630},{"@type":"BreadcrumbList","@id":"https:\/\/www.cotocus.com\/blog\/reuse-a-proven-deploy-script\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.cotocus.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Turn a Deploy Script That Worked Into a Reusable Module"}]},{"@type":"WebSite","@id":"https:\/\/www.cotocus.com\/blog\/#website","url":"https:\/\/www.cotocus.com\/blog\/","name":"Cotocus","description":"Shaping Tomorrow\u2019s Tech Today","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.cotocus.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.cotocus.com\/blog\/#\/schema\/person\/419007bef27e8d85890550d783b96c50","name":"Nikhil Farooqui","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d855702dac00a5af0405bb329101be495718d611233e52c86fe360c8fca6f6dc?s=96&d=mm&r=g","caption":"Nikhil Farooqui"},"url":"https:\/\/www.cotocus.com\/blog\/author\/nikhil-farooqui\/"}]}},"_links":{"self":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/12036","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/comments?post=12036"}],"version-history":[{"count":1,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/12036\/revisions"}],"predecessor-version":[{"id":12159,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/posts\/12036\/revisions\/12159"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media\/12037"}],"wp:attachment":[{"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/media?parent=12036"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/categories?post=12036"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cotocus.com\/blog\/wp-json\/wp\/v2\/tags?post=12036"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}