| #!/bin/bash | |
| # Outputs a pipeline that targets agents that have the same 'name' meta-data | |
| # value as the step that does the pipeline upload. This means that all the | |
| # steps will run on the same agent machine, assuming that the 'name' meta-data | |
| # value is unique to each agent. | |
| # | |
| # Each agent needs to be configured with meta-data like so: | |
| # | |
| # meta-data="name=<unique-name>" |
| dash_id=xxxx | |
| api_key=xxx | |
| app_key=xxx | |
| # 1. export | |
| curl -X GET "https://app.datadoghq.com/api/v1/dash/${dash_id}?api_key=${api_key}&application_key=${app_key}" > dash.json | |
| # 2. edit dash.json | |
| move "graphs", "title", "description" up one level in the json hierarchy, from being beneath "dash" to being at the same level |
Converge is a configuration management tool that makes it easy to manage servers, laptops and other devices.
PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.
Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories
Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.
