[09:10:41] <jayme>	 urandom: I don't have a solid understanding of the aqs chart and that changes would be required (since I don't know the chart at all) but if it's just about adding a config option (and it sounds like it) it would def. be preferred over a new chart. 
[09:11:41] <jayme>	 unfortunately I can't provide exact guidance an what to do since we did not plan for all this so we don't have the capacity right now :/
[09:24:00] <jayme>	 IIUC and it's just about adding the 'tables' map to aqs-http-gateway/templates/_config.yaml - that seems pretty feasible. Maybe sync back with the original chart author (Ben) if there is something against it
[09:24:42] <jayme>	 and if it would be an option to reporpose/rename the chart to something like cassandra-http-gateway for example
[13:42:17] <urandom>	 jayme: ok
[14:27:21] <urandom>	 jayme: actually (now that you mention it) this is really the best explanation for why I went in the direction of a new chart.  Doing it myself, given my lack of experience/knowledge of the subject,  a new chart sits at the intersection of what I can currently figure out for myself (at least with any confidence), and not running the risk of any service using an extant chart.
[14:29:28] <urandom>	 (of breaking an existing service, that is)
[14:30:26] <urandom>	 I realize everyone is busy, but the reuse scenarios discussed are (even) less... newb-friendly
[14:32:11] <jayme>	 I understand it's a bit intimidating. But you will have to implement the exact same thing you would need to extend aqs-http-gateway with in the new chart...so that particular complexity is not going away
[14:33:02] <jayme>	 and we can make sure in the reviews that you don't break AQS deployments. We have a slow but good CI for this
[14:38:28] <jayme>	 I would say it's also quicker to review than a completely new thing. But if you feel really unsafe with this you can ofc. decide to create a new chart. Maybe a generic one that AQS could migrate to in the future
[14:48:55] <urandom>	 I was more commenting on the process here.  I know you're busy, and I do appreciate the help you are providing (I should say so more often), but I go off and try to figure something out on my own, open a review, wait for some feedback, change tack, and then lather, rinse, and repeat
[14:51:50] <jayme>	 ack. Keep/Add me as reviewer so I can check back later or my tomorrow morning
[14:52:02] <urandom>	 kk