cosmos 4.5.2 → 5.0.2.pre.beta2

data/data/config/plugins.yaml

@@ -0,0 +1,217 @@
+---
+VARIABLE:
+  summary: Define a configurable variable for the plugin
+  description: The VARIABLE keyword defines a variable that will be requested for the user to enter during plugin installation.   Variables can be used to handle details of targets that are user defined such as specific IP addresses and ports.  Variables should also be used to allow users to rename targets to whatever name they want and support multiple installations of the same target with different names.
+    Variables can be used later in plugin.txt or in any other configuration file included in a plugin using Ruby ERB syntax.  The variables are assigned to accessible local variables in the file.
+    At a high level, ERB allows you to run Ruby code in configuration files.
+  parameters:
+    - name: Variable Name
+      required: true
+      description: The name of the variable
+      values: .+
+    - name: Default Value
+      required: true
+      description: Default value of the variable
+      values: .+
+INTERFACE:
+  modifiers:
+    <%= MetaConfigParser.load('interface_modifiers.yaml').to_meta_config_yaml(4) %>
+  summary: Defines a connection to a physical target
+  description: Interfaces are what COSMOS uses to talk to a particular piece
+    of hardware. Interfaces require a Ruby file which implements all the interface
+    methods necessary to talk to the hardware. COSMOS defines many built in interfaces
+    or you can define your own as long as it implements the interface protocol.
+  parameters:
+    - name: Interface Name
+      required: true
+      description: Name of the interface. This name will appear in the
+        Interfaces tab of the Server and is also referenced by other keywords.
+        The COSMOS convention is to name interfaces after their targets with
+        '_INT' appended to the name, e.g. INST_INT for the INST target.
+      values: \D\S*
+    - name: Filename
+      required: true
+      description: Ruby file to use when instantiating the interface.
+      values:
+        <%= MetaConfigParser.load('_interfaces.yaml').to_meta_config_yaml(8) %>
+      documentation: Additional parameters are required. Please see the [Interfaces](/docs/v5/interfaces)
+        documentation for more details.
+ROUTER:
+  modifiers:
+    ROUTE:
+      summary: Map an interface to a router
+      description: Once an interface has been mapped to a router, all its received telemetry
+        will be sent out through the router.
+      parameters:
+        - name: Interface
+          required: true
+          description: Name of the interface
+          values: .+
+    <%= MetaConfigParser.load('interface_modifiers.yaml').to_meta_config_yaml(4) %>
+  summary: Create router to receive commands and output telemetry packets from one or more interfaces
+  description: Creates an router which receives command packets from
+    their remote clients and sends them to associated interfaces. They receive telemetry
+    packets from their interfaces and send them to their remote clients. This allows
+    routers to be intermediaries between an external client and an actual device.
+  parameters:
+    - name: Name
+      required: true
+      description: Name of the router
+      values: .+
+    - name: Filename
+      required: true
+      description: Ruby file to use when instantiating the interface.
+      values:
+        <%= MetaConfigParser.load('_interfaces.yaml').to_meta_config_yaml(8) %>
+      documentation: Additional parameters are required. Please see the [Interfaces](/docs/v5/interfaces)
+        documentation for more details.
+TARGET:
+  summary: Define a target
+  description: Defines a target that the plugin adds to the COSMOS system.  Targets are entities that COSMOS can send commands to and receive telemetry from.
+  parameters:
+    - name: Target Folder Name
+      description: The exact name of the target folder in the plugin. ie. targets/<Target Folder Name>
+      required: true
+      values: .+
+    - name: Target Name
+      description: The specific name of this instance of the target in the COSMOS system
+      required: true
+      values: .+
+MICROSERVICE:
+  summary: Define a microservice
+  description: Defines a microservice that the plugin adds to the COSMOS system.  Microservices are background software processes that perform persistent processing.
+  parameters:
+    - name: Microservice Folder Name
+      description: The exact name of the microservice folder in the plugin. ie. microservices/<Microservice Folder Name>
+      required: true
+      values: .+
+    - name: Microservice Name
+      description: The specific name of this instance of the microservice in the COSMOS system
+      required: true
+      values: .+
+  modifiers:
+    ENV:
+      summary: Sets an environment variable in the microservice.
+      description: Sets an environment variable in the microservice.
+      parameters:
+        - name: Key
+          required: true
+          description: Name of the environment variable
+          values: .+
+        - name: Value
+          required: true
+          description: Value of the environment variable
+          values: .+
+    WORK_DIR:
+      summary: Set the working directory
+      description: Working directory to run the microservice CMD in.  Can be a path relative to the microservice folder in the plugin, or an absolute path in the container the microservice runs in.
+      parameters:
+        - name: Directory
+          required: true
+          description: Working directory to run the microservice CMD in.  Can be a path relative to the microservice folder in the plugin, or an absolute path in the container the microservice runs in.
+          values: .+
+    TOPIC:
+      summary: Associate a Redis topic
+      description: Redis topic to associate with this microservice.  Standard COSMOS microservices such as decom_microservice use this information to know what packet streams to subscribe to.  The TOPIC keyword can be used as many times as necessary to associate all needed topics.
+      parameters:
+        - name: Topic Name
+          required: true
+          description: Redis Topic to associate with the microservice
+          values: .+
+    TARGET_NAME:
+      summary: Associate a COSMOS target
+      description: COSMOS target to associate with the microservice.   For standard COSMOS microservices such as decom_microservice this causes the target configuration to get loaded into the container for the microservice.
+      parameters:
+        - name: Target Name
+          required: true
+          description: COSMOS target to associate with the microservice
+          values: .+
+    CMD:
+      summary: Command line to execute to run the microservice.
+      description: Command line to execute to run the microservice.
+      parameters:
+        - name: Args
+          required: true
+          description: One or more arguments to exec to run the microservice.
+          values: .+
+    CONTAINER:
+      summary: Docker Container.
+      description: Container to execute and run the microservice in.
+      parameters:
+        - name: Args
+          required: false
+          description: Name of the container
+          values: .+
+    OPTION:
+      summary: Pass an option to the microservice
+      description: Generic key/value(s) options to pass to the microservice.  These take the form of KEYWORD/PARAMS like a line in a COSMOS configuration file.  Multiple OPTION keywords can be used to pass multiple options to the microservice.
+      parameters:
+        - name: Option Name
+          required: true
+          description: Name of the option
+          values: .+
+        - name: Option Value(s)
+          required: true
+          description: One or more values to associate with the option
+          values: .+
+TOOL:
+  summary: Define a tool
+  description: Defines a tool that the plugin adds to the COSMOS system.  Tools are web based applications that make use of the Single-SPA javascript library that allows them to by dynamically added to the running system as independent frontend microservices.
+  parameters:
+    - name: Tool Folder Name
+      description: The exact name of the tool folder in the plugin. ie. tools/<Tool Folder Name>
+      required: true
+      values: .+
+    - name: Tool Name
+      description: Name of the tool that is displayed in the COSMOS Navigation menu
+      required: true
+      values: .+
+  modifiers:
+    URL:
+      summary: Url used to access the tool
+      description: The relative url used to access the tool.  Defaults to "/tools/<Tool Folder Name>".
+      parameters:
+        - name: Url
+          required: true
+          description: The url.  If not given defaults to tools/<Tool Folder Name>.  Generally should not be given unless linking to external tools.
+          values: .+
+    INLINE_URL:
+      summary: Internal url to load a tool
+      description: The url of the javascript file used to load the tool into single-SPA.  Defaults to "js/app.js".
+      parameters:
+        - name: Url
+          required: true
+          description: The inline url.  If not given defaults to js/app.js.  Generally should not be given unless using a non-standard filename.
+          values: .+
+    WINDOW:
+      summary: How to display the tool when navigated to
+      description: The window mode used to display the tool.  Currently supported modes are INLINE which opens the tool internally without refreshing the page using the Single-SPA framework, and NEW which opens the tool in a new TAB.   A future release will support IFRAME to open external tools in an Iframe within COSMOS.
+      parameters:
+        - name: Window Mode
+          required: true
+          description: INLINE, NEW, or IFRAME
+          values: .+
+    ICON:
+      summary: Set tool icon
+      description: Icon shown next to the tool name in the COSMOS navigation menu.
+      parameters:
+        - name: Icon Name
+          required: true
+          description: Icon to display next to the tool name.   Icons come from Font Awesome, Material Design, and Astro.  See https://vuetifyjs.com/en/components/icons/
+          values: .+
+    CATEGORY:
+      summary: Category for the tool
+      description: Associates the tool with a category.  In a future release this will be able to organize tools into submenus in the Navigation menu.
+      parameters:
+        - name: Category Name
+          required: true
+          description: Category to associate the tool with
+          values: .+
+    SHOWN:
+      summary: Show the tool or not
+      description: Whether or not the tool is shown in the Navigation menu.   Should generally be true, except for the cosmos base tool.
+      parameters:
+        - name: Shown
+          required: true
+          description: Whether or not the tool is shown.  TRUE or FALSE
+          values: .+

data/data/config/screen.yaml

@@ -33,8 +33,7 @@ GLOBAL_SETTING:
       required: true
       description: Widget specific setting name. COSMOS defines several settings
         which apply across many different widget types. However, you can also use
-        the 'RAW' setting which allows any stylesheet values that QT supports.
-        See the QT Stylesheet documentation for more information.
+        the 'RAW' setting which allows any stylesheet values.
       values: <%= %w(TEXTALIGN PADDING MARGIN BACKCOLOR TEXTCOLOR BORDERCOLOR WIDTH HEIGHT RAW) %>
     - name: Setting Value(s)
       required: false
@@ -67,8 +66,7 @@ GLOBAL_SUBSETTING:
       required: true
       description: Widget specific setting name. COSMOS defines several settings
         which apply across many different widget types. However, you can also use
-        the 'RAW' setting which allows any stylesheet values that QT supports.
-        See the QT Stylesheet documentation for more information.
+        the 'RAW' setting which allows any stylesheet values.
       values: <%= %w(TEXTALIGN PADDING MARGIN BACKCOLOR TEXTCOLOR BORDERCOLOR WIDTH HEIGHT RAW) %>
     - name: Setting Value(s)
       required: false
@@ -85,8 +83,7 @@ SETTING:
       required: true
       description: Widget specific setting name. COSMOS defines several settings
         which apply across many different widget types. However, you can also use
-        the 'RAW' setting which allows any stylesheet values that QT supports.
-        See the QT Stylesheet documentation for more information.
+        the 'RAW' setting which allows any stylesheet values.
       values: <%= %w(TEXTALIGN PADDING MARGIN BACKCOLOR TEXTCOLOR BORDERCOLOR WIDTH HEIGHT RAW) %>
     - name: Setting Value(s)
       required: false
@@ -114,8 +111,7 @@ SUBSETTING:
       required: true
       description: Widget specific setting name. COSMOS defines several settings
         which apply across many different widget types. However, you can also use
-        the 'RAW' setting which allows any stylesheet values that QT supports.
-        See the QT Stylesheet documentation for more information.
+        the 'RAW' setting which allows any stylesheet.
       values: <%= %w(TEXTALIGN PADDING MARGIN BACKCOLOR TEXTCOLOR BORDERCOLOR WIDTH HEIGHT RAW) %>
     - name: Setting Value(s)
       required: false
@@ -146,8 +142,6 @@ NAMED_WIDGET:
       required: true
       description: The unique parameters for the given widget type
       values: .+
-STAY_ON_TOP:
-  summary: Force a screen to stay on top of all other windows
 # Even though these are technically SCREEN modifiers we load them at the top_frame
 # level so they appear as available keywords
 <%= MetaConfigParser.load('widgets.yaml').to_meta_config_yaml(0) %>

data/data/config/table_manager.yaml

@@ -49,21 +49,19 @@ TABLE:
       values: ['BIG_ENDIAN', 'LITTLE_ENDIAN']
     - name: Display
       requires: true
-      description: Indicates the table is a ONE_DIMENSIONAL table which is a two
-        column table consisting of unique rows, or a TWO_DIMENSIONAL table with
-        multiple columns and identical rows with unique values
+      description: Indicates the table contains KEY_VALUE rows (e.g. each row is unique),
+        or a ROW_COLUMN table with identical rows containing different values.
       values:
-        ONE_DIMENSIONAL:
-          summary: Declare a key value two column table with unique rows
+        KEY_VALUE:
+          summary: Table rows will be unique items (previously ONE_DIMENSIONAL, now deprecated)
           parameters:
             - name: Description
               requires: true
               description: Description of the table in quotes. The description is
                 used in mouseover popups and status line information.
               values: "['\"].*['\"]"
-        TWO_DIMENSIONAL:
-          summary: Declare a table with multiple columns and identical rows with
-            unique values
+        ROW_COLUMN:
+          summary: Table rows will be indentical with multiple columns (previously TWO_DIMENSIONAL, now deprecated)
           parameters:
             - name: Rows
               requires: true
@@ -80,4 +78,12 @@ SELECT_TABLE:
     - name: Table
       required: true
       description: The name of the existin table
-      values: .*
+      values: .*
+DEFAULT:
+  summary: Specify default values for a SINGLE row in a multi-column table.
+    If you have multiple rows you need a DEFAULT line for each row.
+    If all your rows are identical consider using ERB as shown in the COSMOS demo.
+  parameters:
+    - name: Default values
+      required: false
+      description: A STATE value or data value corresponding to the data type

data/data/config/target.yaml

@@ -1,92 +1,72 @@
 ---
-REQUIRE:
-  summary: Requires a Ruby file
-  description: Ruby files must be required to be available to call in other code.
-    Files are first required from the target's lib folder. If no file is found the
-    Ruby system path is checked which includes the base COSMOS/lib folder.
-  example: REQUIRE limits_response.rb
+TARGET:
+  summary: Defines a new target
+  example: TARGET INST
   parameters:
-    - name: Filename
+    - name: Folder Name
       required: true
-      description: Filename to require. For files in the target's lib directory
-        simply supply the filename, e.g. "REQUIRE my_file". Files in the base COSMOS
-        lib directory also should just list the filename. If a file is in a folder
-        under the lib directory then you must specify the folder name, e.g. "REQUIRE
-        folder/my_file". The filename can also be an absolute path but this is not
-        common. Note the ".rb" extension is optional when specifying the filename.
-      values: .+
-IGNORE_PARAMETER:
-  summary: Ignore the given command parameter
-  description: Hint to other COSMOS tools to hide or ignore this command parameter
-    when processing the command. For example, Command Sender and Command Sequence
-    will not display the parameter (by default) when showing the command and Script
-    Runner code completion will not display the parameter.
-  example: IGNORE_PARAMETER CCSDS_VERSION
-  parameters:
-    - name: Parameter Name
-      required: true
-      description: The name of a command parameter. Note that this parameter will
-        be ignored in ALL the commands it appears in.
-      values: .+
-IGNORE_ITEM:
-  summary: Ignore the given telemetry item
-  description: Hint to other COSMOS tools to hide or ignore this telemetry item
-    when processing the telemetry. For example, Packet Viewer will not display the
-    item (by default) when showing the packet.
-  example: IGNORE_ITEM CCSDS_VERSION
-  parameters:
-    - name: Item name
-      required: true
-      description: The name of a telemetry item. Note that this item will be ignored
-        in ALL the telemetry it appears in.
-      values: .+
-COMMANDS:
-  summary: Process the given command definition file
-  description: This keyword is used to explicitly add the command definition file
-    to the list of command and telemetry files to process.
-  warning: Usage of this keyword overrides automatic command and telemetry file
-    discovery. If this keyword is used, you must also use the TELEMETRY keyword
-    to specify the telemetry files to process.
-  example: |
-    COMMANDS inst_cmds_v2.txt
-    TELEMETRY inst_tlm_v2.txt
-  parameters:
-    - name: Filename
-      required: true
-      description: Name of a command definition file in the target's cmd_tlm directory, e.g. "cmd.txt".
-      values: '.*\.txt'
-TELEMETRY:
-  summary: Process the given telemetry definition file
-  description: This keyword is used to explicitly add the telemetry definition
-    file to the list of command and telemetry files to process.
-  warning: Usage of this keyword overrides automatic command and telemetry file
-    discovery. If this keyword is used, you must also use the COMMAND keyword to
-    specify the command files to process.
-  example: |
-    COMMANDS inst_cmds_v2.txt
-    TELEMETRY inst_tlm_v2.txt
-  parameters:
-    - name: Filename
+      description: The target folder
+      values: .*
+    - name: Name
       required: true
-      description: Name of a telemetry definition file in the target's cmd_tlm
-        directory, e.g. "tlm.txt".
-      values: '.*\.txt'
-AUTO_SCREEN_SUBSTITUTE:
-  summary: Automatically substitute the target's name in screen definitions
-  description: Targets can be renamed when they are declared which would break
-    any screen definitions using the explicit target name. This keyword automatically
-    replaces the target name in the screen definitions with the actual target name.
-  warning: Replaces ALL target names in a screen definition file, so this is not
-    suitable for screens with multiple targets.
-CMD_UNIQUE_ID_MODE:
-  summary: Flags that commands to this target are identified in a mixed variety of ways
-  description: Ideally all commands for a target are identified using the exact same fields in a header
-    for each command.  If  this target identifies packets using different fields for some commands than others,
-    then this flag must be set to force a brute force identification method.
-  warning: Using this mode significantly slows packet identification
-TLM_UNIQUE_ID_MODE:
-  summary: Flags that telemetry to this target are identified in a mixed variety of ways
-  description: Ideally all telemetry for a target are identified using the exact same fields in a header
-    for each packet.  If  this target identifies packets using different fields for some telemetry packets than others,
-    then this flag must be set to force a brute force identification method.
-  warning: Using this mode significantly slows packet identification
+      description:
+        The target name. While this is almost always the same as Folder Name
+        it can be different to create multiple targets based on the same target folder.
+      values: .*
+  modifiers:
+    CMD_LOG_CYCLE_TIME:
+      summary: Command binary logs can be cycled on a time interval.
+      parameters:
+        - name: Time
+          required: true
+          description: Maximum time between files in seconds (default = 600)
+          values: \d+
+    CMD_LOG_CYCLE_SIZE:
+      summary: Command binary logs can be cycled after a certain log file size is reached.
+      parameters:
+        - name: Size
+          required: true
+          description: Maximum file size in bytes (default = 50_000_000)
+          values: \d+
+    CMD_DECOM_LOG_CYCLE_TIME:
+      summary: Command decommutation logs can be cycled on a time interval.
+      parameters:
+        - name: Time
+          required: true
+          description: Maximum time between files in seconds (default = 600)
+          values: \d+
+    CMD_DECOM_LOG_CYCLE_SIZE:
+      summary: Command decommutation logs can be cycled after a certain log file size is reached.
+      parameters:
+        - name: Size
+          required: true
+          description: Maximum file size in bytes (default = 50_000_000)
+          values: \d+
+    TLM_LOG_CYCLE_TIME:
+      summary: Telemetry binary logs can be cycled on a time interval.
+      parameters:
+        - name: Time
+          required: true
+          description: Maximum time between files in seconds (default = 600)
+          values: \d+
+    TLM_LOG_CYCLE_SIZE:
+      summary: Telemetry binary logs can be cycled after a certain log file size is reached.
+      parameters:
+        - name: Size
+          required: true
+          description: Maximum file size in bytes (default = 50_000_000)
+          values: \d+
+    TLM_DECOM_LOG_CYCLE_TIME:
+      summary: Telemetry decommutation logs can be cycled on a time interval.
+      parameters:
+        - name: Time
+          required: true
+          description: Maximum time between files in seconds (default = 600)
+          values: \d+
+    TLM_DECOM_LOG_CYCLE_SIZE:
+      summary: Telemetry decommutation logs can be cycled after a certain log file size is reached.
+      parameters:
+        - name: Size
+          required: true
+          description: Maximum file size in bytes (default = 50_000_000)
+          values: \d+

data/data/config/target_config.yaml

@@ -0,0 +1,94 @@
+---
+REQUIRE:
+  summary: Requires a Ruby file
+  description:
+    Ruby files must be required to be available to call in other code.
+    Files are first required from the target's lib folder. If no file is found the
+    Ruby system path is checked which includes the base COSMOS/lib folder.
+  example: REQUIRE limits_response.rb
+  parameters:
+    - name: Filename
+      required: true
+      description: Filename to require. For files in the target's lib directory
+        simply supply the filename, e.g. "REQUIRE my_file". Files in the base COSMOS
+        lib directory also should just list the filename. If a file is in a folder
+        under the lib directory then you must specify the folder name, e.g. "REQUIRE
+        folder/my_file". The filename can also be an absolute path but this is not
+        common. Note the ".rb" extension is optional when specifying the filename.
+      values: .+
+IGNORE_PARAMETER:
+  summary: Ignore the given command parameter
+  description:
+    Hint to other COSMOS tools to hide or ignore this command parameter
+    when processing the command. For example, Command Sender and Command Sequence
+    will not display the parameter (by default) when showing the command and Script
+    Runner code completion will not display the parameter.
+  example: IGNORE_PARAMETER CCSDS_VERSION
+  parameters:
+    - name: Parameter Name
+      required: true
+      description:
+        The name of a command parameter. Note that this parameter will
+        be ignored in ALL the commands it appears in.
+      values: .+
+IGNORE_ITEM:
+  summary: Ignore the given telemetry item
+  description: Hint to other COSMOS tools to hide or ignore this telemetry item
+    when processing the telemetry. For example, Packet Viewer will not display the
+    item (by default) when showing the packet.
+  example: IGNORE_ITEM CCSDS_VERSION
+  parameters:
+    - name: Item name
+      required: true
+      description:
+        The name of a telemetry item. Note that this item will be ignored
+        in ALL the telemetry it appears in.
+      values: .+
+COMMANDS:
+  summary: Process the given command definition file
+  description:
+    This keyword is used to explicitly add the command definition file
+    to the list of command and telemetry files to process.
+  warning: Usage of this keyword overrides automatic command and telemetry file
+    discovery. If this keyword is used, you must also use the TELEMETRY keyword
+    to specify the telemetry files to process.
+  example: |
+    COMMANDS inst_cmds_v2.txt
+    TELEMETRY inst_tlm_v2.txt
+  parameters:
+    - name: Filename
+      required: true
+      description: Name of a command definition file in the target's cmd_tlm directory, e.g. "cmd.txt".
+      values: '.*\.txt'
+TELEMETRY:
+  summary: Process the given telemetry definition file
+  description: This keyword is used to explicitly add the telemetry definition
+    file to the list of command and telemetry files to process.
+  warning: Usage of this keyword overrides automatic command and telemetry file
+    discovery. If this keyword is used, you must also use the COMMAND keyword to
+    specify the command files to process.
+  example: |
+    COMMANDS inst_cmds_v2.txt
+    TELEMETRY inst_tlm_v2.txt
+  parameters:
+    - name: Filename
+      required: true
+      description: Name of a telemetry definition file in the target's cmd_tlm
+        directory, e.g. "tlm.txt".
+      values: '.*\.txt'
+CMD_UNIQUE_ID_MODE:
+  summary: Command packet identifiers don't all share the same bit offset, size, and type
+  description:
+    Ideally all commands for a target are identified using the exact same bit offset, size,
+    and type field in each command. If ANY command identifiers differ then this flag must be set
+    to force a brute force identification method.
+  warning: Using this mode significantly slows packet identification
+  since: 4.4.0
+TLM_UNIQUE_ID_MODE:
+  summary: Telemetry packets identifiers don't all share the same bit offset, size, and type
+  description:
+    Ideally all telemetry for a target are identified using the exact same bit offset, size,
+    and type field in each packet. If ANY telemetry identifiers differ then this flag must be set
+    to force a brute force identification method.
+  warning: Using this mode significantly slows packet identification
+  since: 4.4.0

data/data/config/telemetry.yaml

@@ -1,5 +1,7 @@
 ---
 TELEMETRY:
+  # Prevent prettier from removing the newline after modifiers:
+  # prettier-ignore
   modifiers:
     <%= MetaConfigParser.load('telemetry_modifiers.yaml').to_meta_config_yaml(4) %>
   summary: Defines a new telemetry packet
@@ -8,39 +10,43 @@ TELEMETRY:
     - name: Target
       required: true
       description: Name of the target this telemetry packet is associated with
-      values: <%= System.targets.keys %>
+      values: .+
     - name: Command
       required: true
-      description: Name of this telemetry packet. Also referred to as its mnemonic.
+      description:
+        Name of this telemetry packet. Also referred to as its mnemonic.
         Must be unique to telemetry packets in this target. Ideally will be as short and clear as possible.
       values: \D\S*
     - name: Endianness
       required: true
       description: Indicates if the data in this packet is in Big Endian or Little Endian format
-      values: ['BIG_ENDIAN', 'LITTLE_ENDIAN']
+      values: ["BIG_ENDIAN", "LITTLE_ENDIAN"]
     - name: Description
       required: false
       description: Description of this telemetry packet which must be enclosed with quotes
-      values: "['\"].*['\"]"
+      values: '[''"].*[''"]'
 SELECT_TELEMETRY:
+  # prettier-ignore
   modifiers:
     <%= MetaConfigParser.load('telemetry_modifiers.yaml').to_meta_config_yaml(4) %>
   summary: Selects an existing telemetry packet for editing
-  description: Typically used in a separate configuration file from where the original
+  description:
+    Typically used in a separate configuration file from where the original
     telemetry is defined to override or add to the existing telemetry definition
   example: SELECT_TELEMETRY SYSTEM LIMITS_CHANGE
   parameters:
     - name: Target Name
       required: true
       description: Name of the target this telemetry packet is associated with
-      values: <%= System.targets.keys %>
+      values: .+
     - name: Command Name
       required: true
       description: Name of the telemetry packet to select
       values: .+
 LIMITS_GROUP:
   summary: Defines a group of related limits Items
-  description: Limits groups contain telemetry items that can be enabled and disabled together.
+  description:
+    Limits groups contain telemetry items that can be enabled and disabled together.
     It can be used to group related limits as a subsystem that can be enabled or disabled
     as that particular subsystem is powered (for example). To enable a group call the
     enable_limits_group("NAME") method in Script Runner. To disable a group call the
@@ -55,7 +61,8 @@ LIMITS_GROUP:
       values: .+
 LIMITS_GROUP_ITEM:
   summary: Adds the specified telemetry item to the last defined LIMITS_GROUP
-  description: Limits group information is typically kept in a separate configuration
+  description:
+    Limits group information is typically kept in a separate configuration
     file in the config/TARGET/cmd_tlm folder named limits_groups.txt. If you want to
     configure multiple target items in a particular group you should put this information
     in the config/SYSTEM/cmd_tlm/limits_groups.txt file. The SYSTEM target is processed
@@ -69,7 +76,7 @@ LIMITS_GROUP_ITEM:
     - name: Target Name
       required: true
       description: Name of the target
-      values: <%= System.targets.keys %>
+      values: .+
     - name: Packet Name
       required: true
       description: Name of the packet