diff --git a/README.md b/README.md
index 4b9679fab..5aaebd6cd 100644
--- a/README.md
+++ b/README.md
@@ -37,7 +37,7 @@ If you would like to self-host Plane, please see our [deployment guide](https://
- **Unified Control:** Centralize management of multi-stage deployment pipelines
across diverse environments.
-- **Flexible Target Support:** Deploy to Kubernetes, cloud functions, VMs, or
+- **Flexible Resource Support:** Deploy to Kubernetes, cloud functions, VMs, or
custom infrastructure from a single platform.
- **Advanced Workflow Orchestration:** Automate sophisticated deployment
processes including testing, code analysis, security scans, and approval
diff --git a/apps/docs/pages/core-concepts/deployments.mdx b/apps/docs/pages/core-concepts/deployments.mdx
index aab97f878..9b6837655 100644
--- a/apps/docs/pages/core-concepts/deployments.mdx
+++ b/apps/docs/pages/core-concepts/deployments.mdx
@@ -84,8 +84,8 @@ Ctrlplane uses a hierarchical structure to manage deployments:
4. **Policy Enforcement**: Inter-environment policies determine when jobs can
run, allowing for controlled progression through environments.
-5. **Job Execution**: Jobs are executed on the identified resources, applying the
- release changes.
+5. **Job Execution**: Jobs are executed on the identified resources, applying
+ the release changes.
## Creating and Managing Deployments
diff --git a/apps/docs/pages/core-concepts/deployments/releases.mdx b/apps/docs/pages/core-concepts/deployments/releases.mdx
index 5eb1aeb88..583158c67 100644
--- a/apps/docs/pages/core-concepts/deployments/releases.mdx
+++ b/apps/docs/pages/core-concepts/deployments/releases.mdx
@@ -41,8 +41,8 @@ set of resources.
## Release Dependencies
Since Ctrlplane is meant for solving the way releases are deployed across
-resources, it's very common to have version dependencies on other deployments. In
-the world of software, this could mean a microservice depends on a specific
+resources, it's very common to have version dependencies on other deployments.
+In the world of software, this could mean a microservice depends on a specific
version of another microservice to ensure it has the required APIs.
In the case of software and infrastructure interactions, this could require a
@@ -73,13 +73,13 @@ other deployments is required.
In most cases, a resource has multiple deployments associated with it, making it
easy to verify if a specific version is deployed on that resource as required by
another deployment. However, complexities arise when dependencies involve other
-resources, where the deployment version might be present on any of these dependent
-resources.
+resources, where the deployment version might be present on any of these
+dependent resources.
-To address this, Ctrlplane uses resource metadata grouping. This mechanism allows
-you to logically group resources based on their metadata attributes. By doing so,
-Ctrlplane can accurately determine which resources to inspect to verify if the
-software has been deployed.
+To address this, Ctrlplane uses resource metadata grouping. This mechanism
+allows you to logically group resources based on their metadata attributes. By
+doing so, Ctrlplane can accurately determine which resources to inspect to
+verify if the software has been deployed.
The idea is to create logical associations between resources that share common
characteristics, such as being part of the same kubernetes cluster. This is
diff --git a/apps/docs/pages/core-concepts/deployments/variables.mdx b/apps/docs/pages/core-concepts/deployments/variables.mdx
index 96cb8b3cd..c7bcc07e1 100644
--- a/apps/docs/pages/core-concepts/deployments/variables.mdx
+++ b/apps/docs/pages/core-concepts/deployments/variables.mdx
@@ -10,8 +10,8 @@ Ctrlplane offers three variable scopes:
1. **System Level**: Global variables applicable to all resources across all
deployments within a system.
-2. **Deployment Level (Wildcard Selector)**: Variables applicable to all resources
- within a specific deployment.
+2. **Deployment Level (Wildcard Selector)**: Variables applicable to all
+ resources within a specific deployment.
3. **Deployment Level (Custom Selector)**: Variables applicable to a subset of
resources within a deployment, based on defined selectors (e.g., metadata,
environment, type).
@@ -56,7 +56,8 @@ Variables can be used in:
endpoints, common timeouts)
- Leverage deployment-level variables for environment-specific settings (e.g.,
staging vs. production configs)
-- Utilize custom selectors for fine-grained control over specific resource groups
+- Utilize custom selectors for fine-grained control over specific resource
+ groups
- Regularly audit and rotate sensitive variables, especially secrets
By mastering Ctrlplane's variable system, DevOps engineers can create flexible,
diff --git a/apps/docs/pages/core-concepts/environments.mdx b/apps/docs/pages/core-concepts/environments.mdx
index a63ca9916..67028490f 100644
--- a/apps/docs/pages/core-concepts/environments.mdx
+++ b/apps/docs/pages/core-concepts/environments.mdx
@@ -31,14 +31,14 @@ resources to the next. These policies can include:
### Resource Filters
-Each environment uses resource filters to dynamically determine which resources are
-associated with it. This feature allows for flexible and automatic assignment of
-resources to environments based on their characteristics.
+Each environment uses resource filters to dynamically determine which resources
+are associated with it. This feature allows for flexible and automatic
+assignment of resources to environments based on their characteristics.
## Dynamic Resource Association
-The use of resource filters enables dynamic addition and removal of resources from
-environments. As a result:
+The use of resource filters enables dynamic addition and removal of resources
+from environments. As a result:
1. Pipelines and deployments automatically run against newly added resources.
2. New software releases or upgrades are automatically applied to relevant
diff --git a/apps/docs/pages/core-concepts/overview.mdx b/apps/docs/pages/core-concepts/overview.mdx
index 57f27e9c3..e401ea31d 100644
--- a/apps/docs/pages/core-concepts/overview.mdx
+++ b/apps/docs/pages/core-concepts/overview.mdx
@@ -10,16 +10,16 @@ import Youtube from "react-youtube";
-**Resources** are entities such as Kubernetes clusters, virtual machines, or other
-logical resources, that the system interacts with. These resources can be added
-manually or through **Resource Providers**, which automate the process by
-continuously monitoring infrastructure, updating resource statuses, and providing
-real-time visibility. Resources are organized into **Environments**, which
-dynamically update based on resource filters, ensuring the right infrastructure is
-always in place for deployments.
+**Resources** are entities such as Kubernetes clusters, virtual machines, or
+other logical resources, that the system interacts with. These resources can be
+added manually or through **Resource Providers**, which automate the process by
+continuously monitoring infrastructure, updating resource statuses, and
+providing real-time visibility. Resources are organized into **Environments**,
+which dynamically update based on resource filters, ensuring the right
+infrastructure is always in place for deployments.
-Once resources and environments are established, **Deployments** come into play. A
-deployment is the process of releasing a specific version of a system into an
+Once resources and environments are established, **Deployments** come into play.
+A deployment is the process of releasing a specific version of a system into an
environment. Each deployment is governed by **Environment Policies**, which
manage how software transitions between environments. When a release is created,
it generates a **Job**, which is executed by **Job Agents** that handle tasks
diff --git a/apps/docs/pages/core-concepts/resources.mdx b/apps/docs/pages/core-concepts/resources.mdx
index 7f7ba6c45..fa8d28a04 100644
--- a/apps/docs/pages/core-concepts/resources.mdx
+++ b/apps/docs/pages/core-concepts/resources.mdx
@@ -26,8 +26,8 @@ import Youtube from "react-youtube";
1. **Creation:**
- API-driven: Programmatically create Resources with custom configurations.
- - Resource Providers: Automated discovery and registration based on predefined
- criteria.
+ - Resource Providers: Automated discovery and registration based on
+ predefined criteria.
2. **Registration:** Link Resources to relevant Environments in Ctrlplane.
@@ -58,7 +58,8 @@ import Youtube from "react-youtube";
## Advanced Concepts
-- **Dynamic Workflows:** Customize actions based on Resource type and Environment.
+- **Dynamic Workflows:** Customize actions based on Resource type and
+ Environment.
- **Complex Filtering:** Combine labels for granular workflow control.
## Resource Registration Details
diff --git a/apps/docs/pages/core-concepts/resources/managing-resources.mdx b/apps/docs/pages/core-concepts/resources/managing-resources.mdx
index 439a9b501..43478ffed 100644
--- a/apps/docs/pages/core-concepts/resources/managing-resources.mdx
+++ b/apps/docs/pages/core-concepts/resources/managing-resources.mdx
@@ -1,27 +1,27 @@
# Managing Resources
As your adoption of Ctrlplane grows, you may find yourself managing hundreds or
-even thousands of resources. This scale of operation requires efficient tools and
-strategies to maintain visibility, control, and agility. Ctrlplane offers
+even thousands of resources. This scale of operation requires efficient tools
+and strategies to maintain visibility, control, and agility. Ctrlplane offers
several features to help you manage large numbers of resources effectively.
## Resource Groups
-Resource Groups are a powerful feature that allow you to organize and manage your
-resources based on their metadata. This grouping mechanism makes it easy to
+Resource Groups are a powerful feature that allow you to organize and manage
+your resources based on their metadata. This grouping mechanism makes it easy to
categorize and find similar resources, providing a more efficient way to manage
your infrastructure at scale.
### How Resource Groups Work
-Resource Groups use the metadata assigned to your resources to automatically group
-them together. Each unique combination of metadata can form a distinct group,
-allowing for flexible and dynamic categorization.
+Resource Groups use the metadata assigned to your resources to automatically
+group them together. Each unique combination of metadata can form a distinct
+group, allowing for flexible and dynamic categorization.
### Creating Resource Groups
-Resource Groups are created automatically based on the metadata you assign to your
-resources. To effectively use Resource Groups:
+Resource Groups are created automatically based on the metadata you assign to
+your resources. To effectively use Resource Groups:
1. Plan your metadata strategy to reflect meaningful categories for your
infrastructure.
@@ -59,8 +59,8 @@ Resource Groups can be incredibly versatile. Here are some common use cases:
### Benefits of Using Resource Groups
-1. **Improved Organization**: Easily manage large numbers of resources by grouping
- them logically.
+1. **Improved Organization**: Easily manage large numbers of resources by
+ grouping them logically.
2. **Efficient Operations**: Quickly identify and work with specific subsets of
your infrastructure.
3. **Consistent Management**: Apply policies, updates, or actions to entire
@@ -126,16 +126,16 @@ You can edit or delete existing views as your infrastructure evolves:
- To delete a view, select it and use the delete option in the view management
interface.
-Resource Views are a valuable tool for maintaining organization and efficiency in
-your resource management workflow, especially as your infrastructure grows in size
-and complexity.
+Resource Views are a valuable tool for maintaining organization and efficiency
+in your resource management workflow, especially as your infrastructure grows in
+size and complexity.
## Locking Resources
Resource locking is a crucial feature that allows you to temporarily prevent any
-pipelines from running against specific resources. This is particularly useful for
-maintenance, troubleshooting, or when you need to ensure that a resource remains
-in a stable state.
+pipelines from running against specific resources. This is particularly useful
+for maintenance, troubleshooting, or when you need to ensure that a resource
+remains in a stable state.
### How Resource Locking Works
diff --git a/apps/docs/pages/core-concepts/resources/metadata.mdx b/apps/docs/pages/core-concepts/resources/metadata.mdx
index c731d03b1..1daa178b7 100644
--- a/apps/docs/pages/core-concepts/resources/metadata.mdx
+++ b/apps/docs/pages/core-concepts/resources/metadata.mdx
@@ -1,9 +1,9 @@
# Resource Metadata
-Resource metadata in Ctrlplane are key-value pairs that provide a flexible way to
-categorize and organize your deployment resources. They play a crucial role in
-defining deployment strategies, filtering resources, and applying configurations
-selectively.
+Resource metadata in Ctrlplane are key-value pairs that provide a flexible way
+to categorize and organize your deployment resources. They play a crucial role
+in defining deployment strategies, filtering resources, and applying
+configurations selectively.
## Configs vs Metadata
@@ -14,20 +14,20 @@ sections in Kubernetes.
### Configs
-Configs are essential for interacting with the resource and should be standardized
-across all types of resources. This standardization ensures that if the same
-pipeline is given two different resources of the same kind, it can use the
-properties in the config to interact with them consistently.
+Configs are essential for interacting with the resource and should be
+standardized across all types of resources. This standardization ensures that if
+the same pipeline is given two different resources of the same kind, it can use
+the properties in the config to interact with them consistently.
In some cases, you might need additional data outside the standard context to
determine how to interact with the resource. In such scenarios, it is acceptable
to include this extra data in the config, but it should be limited to variants
of a given resource and should not impact the primary configuration or behavior.
-In Ctrlplane, configs are used within CI/CD pipelines to interact with resources.
-They define how to deploy or provision the resource. It is crucial that values in
-the config are used to guide these interactions and not to store arbitrary
-metadata.
+In Ctrlplane, configs are used within CI/CD pipelines to interact with
+resources. They define how to deploy or provision the resource. It is crucial
+that values in the config are used to guide these interactions and not to store
+arbitrary metadata.
**Examples of Configs:**
@@ -48,10 +48,10 @@ authenticating with the cluster.
### Metadata
-Metadata in Ctrlplane is used to provide additional information about a resource.
-It consists of key-value pairs that help categorize and organize resources.
-Metadata is not used to define the behavior or configuration of the resource but
-rather to describe it.
+Metadata in Ctrlplane is used to provide additional information about a
+resource. It consists of key-value pairs that help categorize and organize
+resources. Metadata is not used to define the behavior or configuration of the
+resource but rather to describe it.
**Examples of Metadata:**
@@ -82,8 +82,8 @@ requirements.
## Understanding Resource Metadata
-Metadata is attached to resources, allowing you to group and select resources based
-on various criteria. They are particularly useful for:
+Metadata is attached to resources, allowing you to group and select resources
+based on various criteria. They are particularly useful for:
- Organizing resources by environment, region, or purpose
- Applying configurations to specific groups of resources
@@ -94,9 +94,10 @@ on various criteria. They are particularly useful for:
1. **Definition**: Metadata are defined as key-value pairs on individual
resources.
-2. **Flexibility**: You can assign multiple key-value pairs to a single resource.
-3. **Querying**: Ctrlplane allows you to query and filter resources based on their
- metadata.
+2. **Flexibility**: You can assign multiple key-value pairs to a single
+ resource.
+3. **Querying**: Ctrlplane allows you to query and filter resources based on
+ their metadata.
4. **Selective Application**: Use metadata to apply configurations or run
deployments on specific subsets of resources.
@@ -128,21 +129,22 @@ tier: backend
5. **Regular Review**: Periodically review and update your metadata strategy as
your infrastructure evolves.
-By effectively using resource metadata in Ctrlplane, you can create more flexible,
-manageable, and scalable deployment strategies that adapt to your organization's
-evolving needs.
+By effectively using resource metadata in Ctrlplane, you can create more
+flexible, manageable, and scalable deployment strategies that adapt to your
+organization's evolving needs.
## Special Labels
-In Ctrlplane, we have special labels that can be added to resources to enhance the
-user experience in the UI. These labels do not change the core functionality of
-Ctrlplane but provide additional features and visual cues for better usability.
-
-| Label | Description |
-| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ctrlplane/links` | Provides a set of links related to the resource. The value should be a JSON object where the keys are the link names and the values are the URLs. |
-| `ctrlplane/created-by-job-id` | UUID of the Ctrlplane Job that created the resource. |
-| `ctrlplane/external-id` | An external identifier for the resource, which can be used to correlate the resource with resources in other systems. |
-| `ctrlplane/cloud-platform` | The cloud platform the resource is running on (e.g., AWS, GCP, Azure). |
-| `ctrlplane/region` | The geographical region or data center location where the resource is deployed. |
-| `ctrlplane/parent-resource-id` | The UUID of the parent resource, if the resource is a child resource of another resource. |
+In Ctrlplane, we have special labels that can be added to resources to enhance
+the user experience in the UI. These labels do not change the core functionality
+of Ctrlplane but provide additional features and visual cues for better
+usability.
+
+| Label | Description |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ctrlplane/links` | Provides a set of links related to the resource. The value should be a JSON object where the keys are the link names and the values are the URLs. |
+| `ctrlplane/created-by-job-id` | UUID of the Ctrlplane Job that created the resource. |
+| `ctrlplane/external-id` | An external identifier for the resource, which can be used to correlate the resource with resources in other systems. |
+| `ctrlplane/cloud-platform` | The cloud platform the resource is running on (e.g., AWS, GCP, Azure). |
+| `ctrlplane/region` | The geographical region or data center location where the resource is deployed. |
+| `ctrlplane/parent-resource-id` | The UUID of the parent resource, if the resource is a child resource of another resource. |
diff --git a/apps/docs/pages/core-concepts/resources/resource-providers.mdx b/apps/docs/pages/core-concepts/resources/resource-providers.mdx
index 62b46a27d..e939b7c06 100644
--- a/apps/docs/pages/core-concepts/resources/resource-providers.mdx
+++ b/apps/docs/pages/core-concepts/resources/resource-providers.mdx
@@ -10,8 +10,8 @@ up-to-date representation of your deployment landscape.
Resource Providers offer several key advantages over manual creation and
management of resources:
-1. **Automation:** Resource Providers eliminate the need for manual intervention,
- saving time and reducing the potential for human error.
+1. **Automation:** Resource Providers eliminate the need for manual
+ intervention, saving time and reducing the potential for human error.
2. **Dynamic Updates:** As your infrastructure evolves, resource providers
automatically detect changes (e.g., new clusters, servers, or cloud
resources) and update the corresponding resources in Ctrlplane.
@@ -24,9 +24,9 @@ management of resources:
## How Resource Providers Work
-1. **Discovery:** Resource Providers periodically scan your defined infrastructure
- and external systems, identifying potential resources based on configured
- criteria.
+1. **Discovery:** Resource Providers periodically scan your defined
+ infrastructure and external systems, identifying potential resources based on
+ configured criteria.
2. **Registration:** When a new resource is discovered, the resource provider
registers it in Ctrlplane, including relevant metadata such as labels and
associated information.
@@ -40,11 +40,11 @@ Ctrlplane supports various types of resource providers, including:
- **Cloud Resource Providers:** These resource providers integrate with cloud
platforms like AWS, Azure, and Google Cloud, discovering and registering
resources such as virtual machines, Kubernetes clusters, and databases.
-- **Kubernetes Resource Providers:** These resource providers specifically resource
- Kubernetes environments, detecting clusters, namespaces, and other relevant
- objects.
-- **Infrastructure-as-Code Resource Providers:** These resource providers parse your
- infrastructure-as-code definitions (e.g., Terraform, CloudFormation) to
+- **Kubernetes Resource Providers:** These resource providers specifically
+ resource Kubernetes environments, detecting clusters, namespaces, and other
+ relevant objects.
+- **Infrastructure-as-Code Resource Providers:** These resource providers parse
+ your infrastructure-as-code definitions (e.g., Terraform, CloudFormation) to
identify and register resources.
- **Custom Resource Providers:** You can create custom resource providers to
integrate with any system or platform that exposes information about your
diff --git a/apps/docs/pages/core-concepts/resources/schemas.mdx b/apps/docs/pages/core-concepts/resources/schemas.mdx
index 6f4d0dd30..c8068c696 100644
--- a/apps/docs/pages/core-concepts/resources/schemas.mdx
+++ b/apps/docs/pages/core-concepts/resources/schemas.mdx
@@ -25,8 +25,8 @@ of your resource.
## Pre-built Schemas
-Ctrlplane comes with a set of pre-built schemas for common resource types, saving
-you time and effort in defining your own. These schemas cover widely used
+Ctrlplane comes with a set of pre-built schemas for common resource types,
+saving you time and effort in defining your own. These schemas cover widely used
configurations, ensuring consistency and ease of use across different projects.
## Why Use Schema Registration?
@@ -36,7 +36,8 @@ Schema registration offers several benefits:
- **Consistency:** Enforces a uniform structure for resources of the same kind,
ensuring predictable configuration across your deployments.
- **Validation:** Automatically validates the configuration of new or updated
- resources against the registered schema, preventing errors and inconsistencies.
+ resources against the registered schema, preventing errors and
+ inconsistencies.
- **Documentation:** Provides a clear and structured definition of the expected
configuration, aiding collaboration and understanding among team members.
- **Versioning:** Allows for gradual evolution of your schemas without breaking
diff --git a/apps/docs/pages/core-concepts/systems.mdx b/apps/docs/pages/core-concepts/systems.mdx
index e0688f2e8..b37a63e64 100644
--- a/apps/docs/pages/core-concepts/systems.mdx
+++ b/apps/docs/pages/core-concepts/systems.mdx
@@ -99,8 +99,8 @@ Focus on these two crucial aspects:
1. **Deployment Resources:** Ensure that all deployments within a system share
identical deployment resources. This is crucial because deployment pipelines
- are structured to perform deployments on a uniform set of resources within the
- system.
+ are structured to perform deployments on a uniform set of resources within
+ the system.
2. **Environments:** Ensure that all deployments within a system operate within
the same environments and adhere to the same environment policies.
diff --git a/apps/docs/pages/glossary.mdx b/apps/docs/pages/glossary.mdx
index a7231cc3a..340aea2bf 100644
--- a/apps/docs/pages/glossary.mdx
+++ b/apps/docs/pages/glossary.mdx
@@ -3,9 +3,9 @@
**Deployment:** The core process of delivering software or applications to
various environments and resources.
-**Resource:** A specific destination or context where actions are performed during
-a deployment. This can be infrastructure like an EKS cluster or a more abstract
-concept like a custom object.
+**Resource:** A specific destination or context where actions are performed
+during a deployment. This can be infrastructure like an EKS cluster or a more
+abstract concept like a custom object.
**Environment:** A logical grouping of resources representing distinct stages in
the software release process (e.g., QA, Staging, Production).
@@ -22,8 +22,8 @@ rollback strategies.
workflows, independent of specific environments. Can be triggered manually, via
API, or on a schedule.
-**Resource Provider:** An automated process that discovers, registers, and updates
-resources by monitoring infrastructure and external systems.
+**Resource Provider:** An automated process that discovers, registers, and
+updates resources by monitoring infrastructure and external systems.
**System:** A high-level category for grouping deployments that share common
characteristics like environments and policies.
diff --git a/apps/docs/pages/index.mdx b/apps/docs/pages/index.mdx
index aed3d097c..6041f16f9 100644
--- a/apps/docs/pages/index.mdx
+++ b/apps/docs/pages/index.mdx
@@ -79,8 +79,8 @@ your deployment orchestration needs:
- **Sophisticated Rollouts**: Implement complex deployment patterns like canary
releases and blue-green deployments.
-- **Fine-grained Control**: Use labels and resource groups for precise deployment
- resourceing.
+- **Fine-grained Control**: Use labels and resource groups for precise
+ deployment resourceing.
### Scalability and Flexibility
diff --git a/apps/pty-proxy/README.md b/apps/pty-proxy/README.md
index 6597e7db8..5107a4473 100644
--- a/apps/pty-proxy/README.md
+++ b/apps/pty-proxy/README.md
@@ -1,4 +1,4 @@
-# Target Proxy Router
+# Resource Proxy Router
Simple router that redirects web terminal requests to instances and vis-versa.
@@ -15,7 +15,7 @@ sequenceDiagram
opt Init Agent
AG->>PR: Connects to Proxy
- PR->>CP: Register as target
+ PR->>CP: Register as resource
AG->>PR: Sends heartbeat
end
diff --git a/apps/webservice/src/app/[workspaceSlug]/(app)/(job)/job-agents/JobAgentsTable.tsx b/apps/webservice/src/app/[workspaceSlug]/(app)/(job)/job-agents/JobAgentsTable.tsx
index de56f9aa5..9bfdcc5e3 100644
--- a/apps/webservice/src/app/[workspaceSlug]/(app)/(job)/job-agents/JobAgentsTable.tsx
+++ b/apps/webservice/src/app/[workspaceSlug]/(app)/(job)/job-agents/JobAgentsTable.tsx
@@ -40,10 +40,10 @@ const columns: ColumnDef[] = [
];
export const JobAgentsTable: React.FC<{
- activeTargetIds?: string[];
+ activeJobAgentIds?: string[];
jobAgents: JobAgent[];
- onTableRowClick?: (target: JobAgent) => void;
-}> = ({ jobAgents, onTableRowClick, activeTargetIds }) => {
+ onTableRowClick?: (jobAgent: JobAgent) => void;
+}> = ({ jobAgents, onTableRowClick, activeJobAgentIds }) => {
const table = useReactTable({
data: jobAgents,
columns,
@@ -73,7 +73,8 @@ export const JobAgentsTable: React.FC<{
onTableRowClick?.(row.original)}
diff --git a/apps/webservice/src/app/[workspaceSlug]/(app)/(job)/job-agents/integrations/page.tsx b/apps/webservice/src/app/[workspaceSlug]/(app)/(job)/job-agents/integrations/page.tsx
index 8dc15ea73..e4888ca1a 100644
--- a/apps/webservice/src/app/[workspaceSlug]/(app)/(job)/job-agents/integrations/page.tsx
+++ b/apps/webservice/src/app/[workspaceSlug]/(app)/(job)/job-agents/integrations/page.tsx
@@ -49,7 +49,7 @@ export default function AgentPage({
Grant our account the correct permissions and we will manage
- running the target provider for you.
+ running the resource provider for you.
@@ -65,8 +65,8 @@ export default function AgentPage({
Self-hosted Agents
- Agents that you run in your own infrastructure, these target providers
- will automatically register themselves with Ctrlplane.
+ Agents that you run in your own infrastructure, these resource
+ providers will automatically register themselves with Ctrlplane.
@@ -76,7 +76,7 @@ export default function AgentPage({
Custom
- Create custom target providers to import resources.
+ Create custom resource providers to import resources.
With Ctrlplane, you can define, schedule, and monitor jobs across
- various environments and targets. Jobs provide a standardized way to
- manage and track your operations, ensuring consistency and
+ various environments and resources. Jobs provide a standardized way
+ to manage and track your operations, ensuring consistency and
reliability across your entire infrastructure.
- Target metadata groups allow you to organize and categorize your
- targets based on specific metadata keys. By specifying key(s), you
- can group all matching targets and organize them by their
+ Resource metadata groups allow you to organize and categorize your
+ resources based on specific metadata keys. By specifying key(s), you
+ can group all matching resources and organize them by their
corresponding values.
This feature provides a powerful way to visualize and manage your
infrastructure, allowing you to quickly identify and work with
- groups of related targets. For example, you could group targets by
- environment, region, or any other custom metadata you've defined.
+ groups of related resources. For example, you could group resources
+ by environment, region, or any other custom metadata you've defined.
diff --git a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/[groupId]/CombincationsTable.tsx b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/[groupId]/CombincationsTable.tsx
similarity index 95%
rename from apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/[groupId]/CombincationsTable.tsx
rename to apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/[groupId]/CombincationsTable.tsx
index 485df9c81..5062a0bac 100644
--- a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/[groupId]/CombincationsTable.tsx
+++ b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/[groupId]/CombincationsTable.tsx
@@ -25,7 +25,7 @@ export const CombinationsTable: React.FC<{
Combinations
- Targets
+ Resources
@@ -54,7 +54,7 @@ export const CombinationsTable: React.FC<{
);
query.set("filter", filterHash);
return router.push(
- `/${workspaceSlug}/targets?${query.toString()}`,
+ `/${workspaceSlug}/resources?${query.toString()}`,
);
}}
>
diff --git a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/[groupId]/page.tsx b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/[groupId]/page.tsx
similarity index 94%
rename from apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/[groupId]/page.tsx
rename to apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/[groupId]/page.tsx
index 950a92be4..f1f7084eb 100644
--- a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/[groupId]/page.tsx
+++ b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/[groupId]/page.tsx
@@ -5,7 +5,7 @@ import { Badge } from "@ctrlplane/ui/badge";
import { api } from "~/trpc/server";
import { CombinationsTable } from "./CombincationsTable";
-export default async function TargetMetadataGroupPages({
+export default async function ResourceMetadataGroupPages({
params,
}: {
params: { workspaceSlug: string; groupId: string };
diff --git a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/page.tsx b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/page.tsx
similarity index 78%
rename from apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/page.tsx
rename to apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/page.tsx
index 4643cbfa3..dd842d899 100644
--- a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-metadata-groups/page.tsx
+++ b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-metadata-groups/page.tsx
@@ -4,10 +4,10 @@ import { Button } from "@ctrlplane/ui/button";
import { api } from "~/trpc/server";
import { CreateMetadataGroupDialog } from "./CreateMetadataGroupDialog";
-import { TargetGroupsTable } from "./TargetGroupTable";
-import { TargetMetadataGroupsGettingStarted } from "./TargetMetadataGroupsGettingStarted";
+import { ResourceGroupsTable } from "./ResourceGroupTable";
+import { ResourceMetadataGroupsGettingStarted } from "./ResourceMetadataGroupsGettingStarted";
-export default async function TargetMetadataGroupPages({
+export default async function ResourceMetadataGroupPages({
params,
}: {
params: { workspaceSlug: string };
@@ -18,7 +18,7 @@ export default async function TargetMetadataGroupPages({
const metadataGroups = await api.resource.metadataGroup.groups(workspace.id);
if (metadataGroups.length === 0)
- return ;
+ return ;
return (
@@ -32,7 +32,7 @@ export default async function TargetMetadataGroupPages({
-
diff --git a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-providers/ProviderActionsDropdown.tsx b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-providers/ProviderActionsDropdown.tsx
similarity index 92%
rename from apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-providers/ProviderActionsDropdown.tsx
rename to apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-providers/ProviderActionsDropdown.tsx
index fe9254060..b65a7a1a1 100644
--- a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-providers/ProviderActionsDropdown.tsx
+++ b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-providers/ProviderActionsDropdown.tsx
@@ -116,14 +116,14 @@ export const ProviderActionsDropdown: React.FC<{
Delete only the provider: This will set the
- provider field of its targets to null. The first provider to
- add a target with the same identifier will become the new
- owner.
+ provider field of its resources to null. The first provider
+ to add a resource with the same identifier will become the
+ new owner.
- Delete both the provider and its targets:{" "}
+ Delete both the provider and its resources:{" "}
This action is irreversible and will permanently remove the
- provider along with all associated targets.
+ provider along with all associated resources.
- Target Providers are automated processes responsible for
- discovering, registering, and updating targets. They continuously
+ Resource Providers are automated processes responsible for
+ discovering, registering, and updating resources. They continuously
monitor your infrastructure and external systems, ensuring that
Ctrlplane has an accurate and up-to-date representation of your
deployment landscape.
@@ -26,7 +26,7 @@ export const TargetProvidersGettingStarted: React.FC = () => {
diff --git a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-providers/add/GoogleScanerConfig.tsx b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-providers/add/GoogleScanerConfig.tsx
similarity index 82%
rename from apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-providers/add/GoogleScanerConfig.tsx
rename to apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-providers/add/GoogleScanerConfig.tsx
index 2ce704cfd..38fe0d69c 100644
--- a/apps/webservice/src/app/[workspaceSlug]/(app)/(targets)/target-providers/add/GoogleScanerConfig.tsx
+++ b/apps/webservice/src/app/[workspaceSlug]/(app)/(resources)/resource-providers/add/GoogleScanerConfig.tsx
@@ -7,13 +7,13 @@ import {
} from "@ctrlplane/ui/card";
import { Tabs, TabsContent, TabsList, TabsTrigger } from "@ctrlplane/ui/tabs";
-export const GoogleTargetProviderConfig: React.FC = () => {
+export const GoogleResourceProviderConfig: React.FC = () => {
return (
- Google TargetProvider
+ Google Resource Provider
- Scan common targets found in google cloud.
+ Scan common resources found in google cloud.
@@ -43,10 +43,10 @@ export const GoogleTargetProviderConfig: React.FC = () => {