box / box/wavectl

File extensions does not have to be .alert .dashboard

Open
#5 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
16
Forks
10
PR merge metrics
No merged PRs in 30d

Description

We are talking about the files where wavectl stores the json representation of resources. ( Alerts or Dashboards)

The file syntax is actually .json.
So for IDE support aspect, it makes sense to use the extension json.

The wavectl command could read the expected extension in an environment variable. But, I am actually not sure whether this is necessary. I do not think there is anything fundamental in the implementation that would break if we changed the .alert extension to .json.

In wavectl commands the user needs to specify the resource type already. For example
wavectl pull alert
wavectl push dashboard

So as long as the pull and the push command's file extension expectations are the same, using .json should work simply.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.