📄️ Agent
Infrastructural workers in charge of processing core events. They are managed by an agents manager in a computational node. Agents execution are ephemeral.
📄️ Agents Manager
Infrastructural component in charge of handling subsystem operation events and orchestrating agents execution. This is the main component of a computational node. It also ensures the update of agents in the node, self-update and maintenance rounds.
📄️ Artifact
Deployable binaries of a version.
📄️ File forwarding
Mechanism to forward artifacts from one subsystem to another within the same environment. As soon as a version gets published in a source subsystem, its artifact gets pushed as a new version to a target subsystem.
📄️ Attached Transformation
Transformations are post processing modifications attached to subsystems and applied to source files or artifacts. Examples: adding script tags to an html file, obfuscating source files, encrypting content, etc.
📄️ Audit Log
Auditable record of event within an organization.
📄️ Build Agent
Agent responsible for processing build events within a subsystem.
📄️ CED Core
Set of software components that are core to the operation of CED. This is opposed to extensions, which add specific features at certain extensibility points. Extensions can be attached to and detached from the core on runtime.
📄️ CLI Extension
Extension to add commands to the CLI.
📄️ CLI Token
CLI authentication token issued on behalf of a user.
📄️ Computational Node
Computer running one or more agents managers.
📄️ Connection
A connection is an authorized gateway to a service provider. They're used by agents to integrate to service providers.
📄️ Connection Extension
Extension to add a connection type.
📄️ Connection Parameter
A connection parameter is a propery that describes a connection.
📄️ Core Event
Event triggered in the core to be processed in a computational node.
📄️ Custom Build Script
Mechanism to run custom build scripts in the build agent. Usually build steps for a subsystem get described in ced.json. That mechanism can be overridden by creating a custom script for the build agent to run instead of the default logic. In conjunction with external operations, it can be used to delegate builds to external CI/CD platforms like TeamCity.
📄️ Deployment Agent
Agent responsible for processing provision, deploy and clean up events within a subsystem. They integrate with services in service providers in order to manage and deploy their native resources.
📄️ Environment
Environments are isolated copies of a project that allows to move changes up through the different stages in the development process of a solution. Common examples are development, staging and production.
📄️ Exposed Property
A property exposed through the discoverability service from a subsystem to its clients.
📄️ Extension
Software components that attach to an extensibility point to add specfic features. This is opposed to the core which defines the protocol for the extensibility points. Extensions can be attached to and detached from the core on runtime. Extensions can be installed from extensions sources.
📄️ Extensions Source
It's a json file that exposes a list of extensions that can be installed through the CLI and the extensions management commands.
📄️ File forwarding
Mechanism to forward files from one subsystem to another within the same environment. We only support artifact forwarding now.
📄️ GithHub Tokens
Back to index
📄️ Log
Record of event within a project.
📄️ Operation
An operation that takes place as a result of an event.
📄️ Operation State
Represents the state of an operation.
📄️ Organization
An organization is the root entity in CED. It’s a bounded context for projects and users. CED is a Product Central application and uses its API for organizations and users management. Whenever a user gets authenticated through these APIs, CED will be able to know which organization it belongs to.
📄️ Project
A project is an entity that describes a software solution at its root level.
📄️ Project Tab Extension
Extension to add a project tab.
📄️ Index
1. Agent
📄️ Root Tab Extension
Extension to add a root tab.
📄️ Secrets
Back to index
📄️ Service Provider
Platforms that provide integrated services to CED. Examples: Azure, AWS, Google Cloud, etc.
📄️ Source files
Files that contain original or essential data that is the starting point for generating artifacts of a version.
📄️ Subsystem
A subsystem represents a piece of software that can be configured, deployed and interact with other subsystems, describing the graph of dependencies among the different pieces in a solution.
📄️ Subsystem Client
Link between two subsystems that expose configuration from one to another through the discoverability service. If subsystem A is a client of subsystem B, this means that A depends on B and B exposes properties for A to work.
📄️ Subsystem Extension
Extension to add a subsystem type.
📄️ Subsystem Operation
An operation that takes place in the context of a subsystem as a result of a subsystem operation event.
📄️ Subsystem Operation Event
Events in the lifecycle of a subsystem.
📄️ Subsystem WebHook
Web hooks get triggered on subsystem events and operations. Can be applied at a subsystem level or project level.
📄️ Template
Recipe for a solution in CED, serialized in a yaml file. It allows you to deploy templates and predefined solutions.
📄️ Template Agent
Agent responsible for processing deploy-template event within an organization.
📄️ Template Deployment
Represents the deployment of a template in an organization.
📄️ Template Deployment Reports
Back to index
📄️ Transformation Extension
Extension to add a transformation type.
📄️ Version
A version represents the unique state of a subsystem as it is developed and released.
📄️ Version Validation
Represents the state of a validation against a version