Initial changes for dashboards automation #78
Conversation
vishnuchalla
force-pushed
the
vchalla
branch
from
8a4f4a6 to
e33636a
Compare
vishnuchalla
force-pushed
the
vchalla
branch
from
e33636a to
7ecdf68
Compare
| dashboard=$(cat ${full_path}); | ||
| for t in rendered/**/*.json; do | ||
| echo "Importing ${t}"; | ||
| dashboard=$(cat ${t}); | ||
| echo "{\"dashboard\": ${dashboard}, \"overwrite\": true}" | | ||
| curl -k -Ss -XPOST -H "Content-Type: application/json" -H "Accept: application/json" -d@- |
There was a problem hiding this comment.
The internal grafana won't be accessible from outside
There was a problem hiding this comment.
Yes, Those actions in workflows are not of any use right now. They just help us to do some sanity checks, if we are able to build jsons and deploy them into grafana. To start with lets keep it that way and our plan is to extend the same actions for our automatic deployments in future.
There was a problem hiding this comment.
As is now this workflow is gonna fail, is that expected?
There was a problem hiding this comment.
Yes it is expected and I am planning to take it outside of this PR scope. It has been failing since a while: https://github.com/cloud-bulldozer/performance-dashboards/actions/runs/6252714644/job/16976553973 as github actions won't be able to reach our observability cluster.
vishnuchalla
force-pushed
the
vchalla
branch
from
7ecdf68 to
c61457a
Compare
vishnuchalla
force-pushed
the
vchalla
branch
from
c61457a to
f504c80
Compare
Modified: Internal logic for creating/updating dashboards Deleted: Removed old logic as it is not flexible for automation
vishnuchalla
force-pushed
the
vchalla
branch
from
f504c80 to
2321a75
Compare
Type of change
Added: Support for multiple multiple folders, python client
Modified: Internal logic for creating/updating dashboards
Deleted: Removed old logic as it is not flexible for automation
Description
As an initial step in our plan to automating dashboards. Adding support for multiple folders and integrating python client for ease of maintenance.
Related Tickets & Documents
Checklist before requesting a review
Testing
Tested in the local environment, using the same old methodology.
maketo generate therenderedfolderdittybopper/syncer/deploy.sh.