An extensible auto-tagger for IaC files that links cloud resources back to the codified infrastructure that created them.
Yor is an extensible auto-tagging tool for Infrastructure as Code (IaC) files that automatically adds consistent tags to resources defined in Terraform, CloudFormation, and Serverless frameworks. It solves the problem of untagged or inconsistently tagged cloud resources by linking them back to the codified infrastructure that created them, enabling better traceability and governance.
DevOps engineers, platform teams, and cloud infrastructure developers who manage IaC at scale and need to enforce tagging policies, track changes, and maintain resource attribution across their cloud environments.
Developers choose Yor because it automates a tedious but critical aspect of cloud management, integrates seamlessly into existing CI/CD pipelines and local workflows, and provides extensibility for custom tagging logic without requiring deep changes to their IaC.
Extensible auto-tagger for your IaC files. The ultimate way to link entities in the cloud back to the codified resource which created it.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically adds git metadata like commit hash, repository, and modifier to resources, enabling precise attribution without manual updates, as highlighted in the change management feature.
Supports custom taggers and tag groups via the --custom-tagging flag, allowing teams to implement bespoke logic, referenced in the usage examples and CUSTOMIZE.md.
Runs as a GitHub Action, pre-commit hook, standalone CLI, or Docker container, providing seamless integration into diverse workflows, detailed in the installation section.
Includes a dry-run option to preview tags before applying changes, reducing risk of unintended modifications, demonstrated in the CLI usage examples.
Only supports Terraform, CloudFormation, and Serverless Framework, excluding popular IaC tools like Pulumi or CDK, as admitted in the README's feature list.
Implementing custom taggers requires Go knowledge and editing configuration files, which can be a barrier for non-developer teams, implied by the need for external plugins and CUSTOMIZE.md.
Automatically modifies IaC files, which can cause merge conflicts in version control or break existing tag structures, though skips are provided to mitigate this.