Glossary
This section defines key Code Pipes terms.
Term | Definition |
---|---|
Organization | Organizations are used to control tenancy. Most APIs come through a single organization, so this is the level where most RBAC occurs. You can create an organization and then invite other users to join your organization with a specified RBAC role. |
Members | Members refer to the users who are part of an organization and have been invited to join with a specific RBAC role. |
Credentials | Credentials are the necessary authentication details required for accessing external systems such as GitHub, GCP, and AWS. They can be applied at the environment or project level. |
Project | Projects are defined within an organization and can contain related environments, applications, and deployments. They also include a list of environment, IaC an app variables, credentials required for accessing external systems, and the default policy set for IaC validation. |
Environment | An environment is a part of a project and holds the infrastructure that a project's applications will use. It specifies the location where applications are deployed. Environments can be created for different needs, such as development, testing, and production. They include a list of Git repos, IaC code, environment/terraform variables, credentials, and a policy set for validation. |
Environment classification | Environment classification refers to categorizing environments based on their purpose or target audience. Common classifications include development, test, and production environments. |
Application | Applications are entities within a project that are deployed in environments. |
App artifacts | App artifacts are the compiled or packaged components of an application, such as containers repository and code repository. |
Container repository | A container repository is a storage location for container images that are used for deploying applications in containers. |
Code repository | A code repository is a version control system or storage location for source code. It holds the application's codebase and infrastructure code (IaC). |
App dependencies | App dependencies refer to the terraform modules from terraform registry or any other git source, that an application relies on to function properly. |
Integration pipeline | An integration pipeline refers to a series of automated steps and processes that integrate various components of an application (eg. build,test,secure). |
Git Trigger | A Git Trigger is a mechanism that initiates a pipeline or workflow when changes are made to a specific branch, commit, or tag in a Git repository. |
App deployments | App deployments involve the process of deploying an application to a specific environment, making it available for use. |
Policy set | A policy set is a collection of predefined rules or policies that are applied to validate the Terraform code used for infrastructure provisioning and management. |
Environment set | An environment set refers to a group or collection of related environments that has some promotional relationship defined. |
Deployment pipeline | A deployment pipeline is a sequence of actions and tasks that automate the deployment of an application or system. It typically includes deploying the application to a target environment. |
Validation pipeline | A validation pipeline is a series of automated steps and checks that validate the correctness and integrity of configurations, or infrastructure. It ensures that the deployed application meets the defined compliance and quality standards. |
Destroy pipeline | A destroy pipeline is a set of automated steps and processes that tear down or destroy the resources and infrastructure associated with an application or system. It is used when removing an application or decommissioning an environment. |
Code promotion | Code promotion refers to the process of promoting or moving code and application changes from one environment to another, typically following a predefined workflow or promotion sequence. |
Hierarchy | Code Pipes entities follow a parent/child hierarchy, with organizations at the top, followed by projects, environments, and applications. Lower-level settings in the hierarchy override higher-level settings. |
Updated over 1 year ago