Cloud Foundations

Cloud Foundations owns the shared Azure infrastructure the rest of SAIF builds on: the docs.saif.com publishing platform and its Front Door, WAF, and Private Link wiring, the custom saif.com subdomain pipeline, the shared saif-docs Azure AI Search index, and the orchestrator pipelines that deploy all of it. These pages document how to consume that infrastructure and why it is shaped the way it is.

  • Deploying to the Shared Docs Site

    Pipeline files, variables, and mkdocs.yml settings a repo needs to publish docs to docs.saif.com, plus the frontmatter and containerFolderName rules the search index depends on.

    Read the guide

  • Custom Subdomains

    How to add a saif.com subdomain through subdomains.tfvars, what Terraform provisions in Front Door, WAF, and Route53, and the manual internal DNS CNAME request it does not cover.

    Read the guide

  • Pulumi Cloud OIDC from Azure DevOps

    How pipelines authenticate to Pulumi Cloud and Azure with workload identity federation instead of stored tokens, and how infra/bootstrap creates both sides of the trust.

    Read the guide

  • Orchestrator Pipelines and Required Template Checks

    Why Azure DevOps' CheckRequiredTemplate never matches an orchestrator-shaped pipeline, and how cloud-foundations moved to a root extends with inlined deployments and a pinned templates ref.

    Read the guide

  • saif-docs Search Index Reference

    Field contract, ranking behavior, and known limitations of the shared Azure AI Search index, covering description, app, repo, section, format, deduplication, and backfill.

    Read the reference