Improved error messages

[t-ikeda-sti]

User Story

The developer wants to resolve errors on his own from the error messages from the CLI. For this reason, they want to get clear error messages from dacrane.

Acceptance Criteria

(TBD)

[t-ikeda-sti]

error kinds

• static validation
  • command
  • typo
    • command name (ex: destory) -> use cobra validation
    • flag name (ex: --argment) -> use cobra validation
    • argument -> need custom validation
    • module name
    • instance name
  • --argument flag value format
    • yaml format -> need custom validation
    • module parameter (JSON Schema) -> need custom validation
  • --argument flag
    • yaml semantic (a: ${{ 1 + "a" }}) -> need custom validation
  • deployment code -> need custom validation
  • yaml syntax error
  • expression (in ${{}}) syntax error
  • type error
    • (ex: if: ${{ 1 + 1 }} # expected to bool type, but number )
    • (ex: ${{ modules.foo }} # foo is not exists)
  • circular referencing
    • (ex: foo -(ref)-> bar, bar -(ref)-> foo)
• dynamic error handling
  • runtime
  • provider error (create/update/delete)
    • dacrane will make it as far as it can be made until an error occurs.
  • unknown error

[t-ikeda-sti]

By next week, I will come up with a policy for specifications.