I am a waiter at a country club . We get paid hourly and the members are told not to tip us . During the slow season , i might have one or two tables per shift and still get paid handsomely . Your restaurants probably like you to be paid based on how busy it is . Not how long youre in the building . If its busy and the restaurant makes money then you make money . If not , you dont . THis isn ' t a problem at my club because its non profit the members are the owners essentially and my managers arent concerned about turning a profit off of the people that pay to keep the place standing . <| sep |> Yeah I ' m not too fussed about what appears in reports or on the master or puppetdb etc . The only people who will be able to see it there will already know the info , so that ' s fine . The main concern was around the keys being stored in git . I think using eyaml for that is probably going to be ok . It will solve my most immediate problem , and I ' ll think about it some more for a couple of similar things . Thanks heaps to everyone , thats been a good help .