Harness Entity Reference
The term entity is used to refer to the cross module components of Harness. Most entities can be created at the account, organization, and project level.
In this topic:
- Examples of Entities
- Entity Identifiers
- Entities are Connected
- Entity Deletion
- Related Reference Material
Examples of Entities
Here are some example of entity types in Harness:
- Users Group
- Service Definition
- Infrastructure Definition
- Secret Managers
Most Harness entities and resources include a unique Id (Identifier) that is immutable once the entity is created.
Identifiers provide a permanent way to refer to an entity, and avoid issues that can arise when a name is changed.
Entity Id Scope
Entity Id is scoped at the level where it is created. For example, two Pipelines can have the same Id if they are in different Projects.
Entity Id has the following rules:
- There cannot be 2 or more Orgs with the same Id within the account.
- There cannot be 2 or more Projects with the same Id within the Org.
- There cannot be 2 or more Pipelines with the same Id within the Project.
- There cannot be 2 or more stages with the same Id within the Pipeline.
- There cannot be 2 or more steps with the same Id within the stage.
The identifier must start with
_ and can then be followed by
The Id should not be any of the following words:
If within the retention policy, user should be able to restore an entity that was deleted.
- All entities that are restored should be visible in their respective areas as they were before the deletion took place
- When restoring a pipeline, all its deployments should appear in the respective reports
- When restoring a user, its respective roles should be re-applied manually (the same roles that were applied before, will not be reapplied automatically)