For things like reporting a deployment to New Relic, it would be useful to be able to refer to the person's name entered on the big red button page.

As far as I can tell, there is no way to get at this from inside the script that contains the pre_update(), update() and deploy() tasks.

It's not clear under what license this code is being distributed. Please add a LICENSE file to clarify. Otherwise no one knows what rights they have when copying it (or even whether they can copy it).

Currently $servername/chief/ returns a 404

Make it so $servername/chief/ lists available Chief apps, instead of returning 404

It's needed for a functional deployment

If you are amazing superfly devops person and do lots of deployments or if you hook up your chief to a cron script that runs every 5 minutes for a month, you can end up with a lot of history.

At that point, the history page may not load in time and kick up an ISE. For example, the input-dev history page is now 1.3mb and occasionally kicks up an ISE.

I suspect it'd be better if history was paginated.

Review making //history/ read logs from disk and not just memory

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC001)

It'd be good to have a quickstart for contributors. The instructions in the README seem more involved than I'd like. It might be fine to just make the defaults friendlier for the "you just cloned this repository for the purposes of contributing to this project" context.

It'd be good to have tests.

Both of these are generally good project things. I'll look into fixing both of them if I find myself or others contributing more to chief. I figured it was a good idea to jot it down in the issues list in case someone else had a hankering to work on them.

Having a .json settings file would make it easier to make an admin utility

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• the wiki has been disabled, as it was not used

These were made as the result of a recent automated defacement of publically writeable wikis.

Needs RPMs for webops deployments.