You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
alertwavectl pull
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.
The text was updated successfully, but these errors were encountered: