GitLab

• Allowed actions are [waypoint_list]
• Min and max actions are 1
• How to include in planning_configuration
  • Could include the schema directly in the planning_configuration message although that means making a schema to validate a schema?
  • Better might be to define a slocum_mission_plan as part of the schema and say "your mission_plan payload should validate against the slocum_mission_plan schema".

how does this look in planning_configuration

{
  "capabilities": {
    "payloads": {
      "mission_plan": {
        "type": "generated",
        "valid_actions": ["action_waypoint_list"],    // references action schema
        "validate_with": "mission_plan_slocum"        // or "mission_plan_masdt" min/max rules 
        // we don't need both of these - one or the other is probably enough
      },
      "instruction_set": {
        "type": "static",
        "options": [
           // list of instruction set payloads containing b64 encoded files
           // chosen option can be included as-is as message payload
        ] 
      }
    }
  }
} 

changed the description

I guess there are a few alternatives to validating that there is only one action in the mission:

1. Instead of action_type=waypoint_list have action_type=waypoint (more like what we have already) then the SFMC adapter compiles the list of waypoint actions into a list of waypoints in 1 goto file
2. We keep waypoint_list but don't require a max of 1. You can still make 2 lists of waypoints into 1 list of waypoints and create 1 goto file
3. We don't bother changing the mission plan at all (apart from switching to GeoJSON) and just parse the waypoints out of the action schema we already have.

I had originally been thinking about this as creating a correspondence where 1 mission action = 1 slocum file but we're no longer working like that so there's no reason to do that.

If we keep the action schema pretty much as is we can just have

{
  "capabilities": {
    "payloads": {
      "mission_plan": {
        "type": "generated",
      },
      "instruction_set": {
        "type": "static",
        "options": [
           // list of instruction set payloads containing b64 encoded files
           // chosen option can be included as-is as message payload
        ] 
      }
    }
  }
} 

This is handled in #62 (closed)

closed