Skip to main content
⏳ Estimated read time: 5 min read

Add New Resource

The Add New Resource panel in the Topology Canvas enables you to add cloud resources by simply dragging the desired resource onto the canvas. It offers multiple categories to accommodate diverse infrastructure needs.

Add Resources to Your Topology​

Follow these simple steps to add resources to your topology canvas:

  1. Open the Add New Resource panel by clicking the "+ Add New Resource" button.
  2. Browse or search for the resource you want to add.
  3. Click and drag the resource onto your canvas.
  4. Configure the resource properties in the panel that appears.
  5. Your resource is now ready to be connected with other resources in your topology.

Add Resources to Your Topology​

Follow these simple steps to add resources to your topology canvas:

  1. Open the Add New Resource panel by clicking the "+ Add New Resource" button.
  2. Browse or search for the resource you want to add.
  3. Click and drag the resource onto your canvas.
  4. Configure the resource properties in the panel that appears.
  5. Your resource is now ready to be connected with other resources in your topology.

Types of Resources​

StackGen supports adding the following resource types to your topology canvas:

Cloud Provider​

Provides a comprehensive catalog of resources from the Cloud Provider you have selected at the time of appStack creation.

Supported Cloud Providers: AWS, Azure, GCP, and Civo Cloud

Features​

  • Drag-and-drop functionality for adding compute, networking, storage, and IAM resources.
    • Displays resource-specific icons and details for easy identification.
    • Supports multi-cloud architecture design within a single canvas.

Check the full list of supported resources at Supported Technologies.

Helm​

Facilitates the integration of Helm-based Kubernetes resources directly into the Topology Canvas.

Features​

  • Import Helm charts from Git-based repositories.
  • Edit workload resource bundles within the canvas.
  • Configure Kubernetes components such as:
    • Ingress
    • Horizontal Pod Autoscaler (HPA)
    • Service Accounts (inside or outside the resource bundle)

Use Case: Easily manage Kubernetes deployments alongside cloud infrastructure for unified visibility.

General​

Includes custom modules and generic infrastructure components that are not tied to a specific cloud provider.

Features​

  • Define abstract resource types to model non-cloud-specific components.
  • Map abstract resources to specific cloud services during later configuration stages.
  • Useful for hybrid and multi-cloud environments where certain resources may exist outside of traditional cloud ecosystems.

Resource Pack​

Enables users to create and manage predefined infrastructure templates for consistent, reusable deployments.

Features​

  • Import, customize, and deploy modular resource configurations.
  • Simplify complex deployments by grouping commonly used resources into a single pack.
  • Supports versioning for tracking changes across different deployments.

Example: A Resource Pack for a standard web application stack might include:

  • Load Balancer
  • Application Servers
  • Database
  • Required IAM Roles
info

Starred and Recent Resources in a team are shared among the team members. They are private only in Personal Workspaces.

Recent and Starred Resources​

The Add New Resource panel allows you to quickly access your frequently used and favorite resources through the Recent and Starred tabs.

Recent Resources​

This tab displays resources you've recently used in your topologies, making it easy to find and reuse common components.

Starred Resources​

You can mark resources as favorites by clicking the star icon next to any resource. These starred resources will appear in this tab for quick access.

Resource Sharing Behavior​

When working with Recent and Starred resources, it's important to understand how they are shared:

In Personal Workspaces​

  • Recent and Starred resources are private to you.
  • Only you can see the resources you've marked as favorites or recently used.

In Team Workspaces​

  • Recent and Starred resources are shared across the entire team.
  • When you star a module, it becomes accessible to all team members in their Starred tab.
  • If another team member removes a star from a resource, it will be removed from the Starred tab for all team members.
  • Recent resources are also visible to all team members, even if they personally didn't use that resource.

This sharing behavior promotes collaboration and consistency within teams but means that your starred resources may change if modified by other team members.

Custom Module Permission Scopes​

When working with custom modules, you'll see different permission scopes that determine who can access them:

  1. Team Scope: The custom module is shared with your team.
  2. Enterprise Scope: The custom module is shared enterprise-wide.
  3. Personal/Workspace Scope: The custom module is created in your personal workspace and will be available only for your personal use.
Last updated on