Skip to content

epic: Migrate TierPoint Azure Local content to AzureLocal Cloud organization #10

@kristopherjturner

Description

@kristopherjturner

Overview

This is the parent tracking issue for migrating two private TierPoint repositories into the AzureLocal Cloud organization. These repos contain a comprehensive Azure Local deployment solution (docs + automation) that was developed for TierPoint's managed services practice. The content is highly valuable and transferable — the core Azure Local knowledge, implementation runbooks, and PowerShell automation are vendor-agnostic once company-specific references are removed.

Source Repositories

Repo Location Type Size
product-azure-local-anywhere Local only Documentation — Docusaurus site ~321 files (250 .mdx, 56 .json, 9 .md, 6 .drawio)
prodtech-docs-azl-toolkit Local only Toolkit — scripts, configs, solutions ~597 files (227 .ps1, 28 .json, 10 .tf, 7 .bicep, 9 .yml)

These two repos were designed as a paired system: the docs repo has step-by-step procedures, and the toolkit repo has matching scripts in a mirrored folder structure.

Migration Targets

Source Target Target Repo
product-azure-local-anywhere Migrate docs into azurelocal.github.io Docusaurus site AzureLocal/azurelocal.github.io (this repo)
prodtech-docs-azl-toolkit Create new repo AzureLocal/azurelocal-toolkit and migrate New repo to be created

Critical Requirements (Apply to BOTH Sub-Tasks)

1. Company Reference Removal (MANDATORY)

ALL references to the following MUST be removed or replaced:

Find Replace With Count (Docs) Count (Toolkit)
TierPoint Azure Local Cloud or Hybrid Cloud Solutions 199 145
prodtech / Product Tech / ProdTech Azure Local Cloud 51 111
PCS (company context) Remove or replace contextually 7 6
TierPoint tenant IDs Example/placeholder IDs scattered 47 (in tplabs.yml)
team-prodtech@ emails AzureLocal org contact scattered scattered
gitlab.com/tierpoint/prodtech/ URLs GitHub AzureLocal URLs scattered scattered

~493 total matches across both repos. Each must be reviewed — some are simple find/replace, others need contextual rewriting.

2. Branding Standards

  • Organization: Azure Local Cloud (or AzureLocal in GitHub context)
  • Consulting brand: Hybrid Cloud Solutions
  • Example company: Infinite Improbability Corp (IIC) — already used in these repos, keep as-is
  • Fictional domain: iic.local / improbability.cloud — keep as-is

3. Content That Should NOT Be Migrated

  • TierPoint-specific B2B configuration — contains TierPoint IP for cross-tenant setup
  • PCS-specific and ProdTech-specific pipeline approaches
  • GitLab CI/CD specifics — TierPoint uses GitLab; we use GitHub
  • Execution logs (214 files) — evidence of production use, do not migrate
  • Terraform state files — security concern
  • Environment-specific config files — contain real Azure resource IDs

Sub-Tasks

Success Criteria

  • Zero references to TierPoint, ProdTech, PCS in any migrated content
  • All migrated content follows AzureLocal Cloud standards
  • Documentation is live on the Docusaurus site
  • Toolkit repo is created with clean history (no legacy commits with company data)
  • Detailed migration plans exist for both sub-tasks before work begins
  • Variable structure decision made and implemented (infrastructure.yml → variables.yml)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions