Instruqt Labs (beta)
  • Instruqt
  • Getting started
    • Setting up Version Control
    • Install Instruqt CLI
    • Creating your first lab
    • Configuration basics
    • Exploring the lab configuration
    • Adding your first chapter
    • Configuring sandboxes
    • Adding quizzes
    • Adding tasks and gating content
    • Finishing up
  • Documentation
    • Writing Lab Content
      • Project Structure
      • Markdown and Components
    • Integrations
      • Version Control
    • Lab reference
      • Content
        • Lab
        • Page
        • Activities
          • Task
          • Quiz
            • Multiple Choice
            • Single Choice
            • Text Answer
            • Numeric Answer
        • Layout
        • Tabs
          • Terminal
          • Service
          • Editor
          • External Website
          • Note
      • Sandbox
        • Containers
          • Container
          • Sidecar Container
        • Kubernetes
          • Cluster
          • Config
          • Helm
        • Nomad
          • Cluster
          • Job
        • Networking
          • Network
          • Ingress
        • Cloud Accounts
          • AWS
          • Azure
          • Google Cloud
        • Terraform
        • Template
        • Exec
        • Copy
        • Certificates
          • Root
          • Leaf
        • Random
          • Number
          • ID
          • UUID
          • Password
          • Creature
      • Functions
    • Tools
      • Instruqt CLI
    • Glossary
Powered by GitBook
On this page
  • Editor
  • Workspace
  • Examples
Edit on GitHub
Export as PDF
  1. Documentation
  2. Lab reference
  3. Content
  4. Tabs

Editor

Editor

The editor resource represents a target that a tab in the layout can point at. It contains all the configuration that the participants proxy needs to route to the target service behind it.


resource "editor" "name" {
  ...
}

Attributes

Attribute
Description

Directory trees that are exposed as workspaces in the editor.

Computed Attributes

These attributes are computed when the config is parsed and applied, and are therefore only known at parsetime or runtime.

Attribute
Description

Meta ID meta.id string

The full ID of the resource e.g. `resource.type.name`. This is computed from the full resource path:

Meta Type meta.type string

The type of the resource. This taken from the type label of the resource definition.

Meta Name meta.name string

The name of the resource. This taken from the name label of the resource definition.


Workspace


resource "editor" "name" {
workspace "name" {
  ...
}
}

Attributes

Attribute
Description

Name name required type: string

The name of the workspace.

Directory directory required type: string

The directory to open in the workspace.

The target host that the directory should be opened on.

Computed Attributes

These attributes are computed when the config is parsed and applied, and are therefore only known at parsetime or runtime.

Examples

Full Example


resource "editor" "code" {
  workspace "assets" {
    directory = "files"
  }

  workspace "vault_config" {
    target = resource.container.ubuntu
    directory = "/etc/vault.d"
  }
}
PreviousServiceNextExternal Website

Last updated 1 month ago

Workspaces workspace type: []block

Target target type: Reference to

workspace "config" {
  target = resource.container.vault
  directory = "/etc/vault"
}
// given the following resource
resource "container" "ubuntu" {
  ...
}

// the resulting id will be
resource.container.ubuntu
// given the following resource
resource "container" "ubuntu" {
  ...
}

// the resulting type will be
container
// given the following resource
resource "container" "ubuntu" {
  ...
}

// the resulting name will be
ubuntu
workspace "name" {
  ...
}
directory = "/etc/vault"
target = resource.container.vault
Container
Workspace