Not really. I'll just rewrite them in go if there isn't a tool I need, or it the interface is crappy. I have built a few databases from scratch, so writing simple tools is trivial.
On Mon, 2 Nov 2020, 5:25 pm Tyler Compton, <xavi...@gmail.com> wrote: > I saw yq but it seemed like it was written in python, which I have no time >> for. >> > > You're going to be limiting your tooling options quite a bit in that case > :) > > On Mon, Nov 2, 2020 at 8:49 AM alex breadman <a...@cpu.host> wrote: > >> Thanks for the reply. >> >> I just did it for fun actually, and for the purpose of learning to make >> GitHub actions. >> >> I saw yq but it seemed like it was written in python, which I have no >> time for. >> >> The dasel one looks the best imo. >> >> >> >> On Mon, 2 Nov 2020, 4:41 pm Howard C. Shaw III, <howardcs...@gmail.com> >> wrote: >> >>> If written because you needed experience and writing a program to >>> perform a task you need done is better for learning, then go you! But if >>> you are legitimately looking to solve a problem, you might want to throw a >>> quick search out first before implementing Yet Another X. >>> >>> For yamlfukr update file.yaml key value: >>> https://github.com/mikefarah/yq >>> yq w -i file.yaml key value >>> >>> yq also supports b.c.d.e key names to edit deeper values. >>> >>> https://github.com/TomWright/dasel >>> >>> dasel put string -f file.yaml -p yaml "key" value >>> >>> dasel also supports b.c.d.e key names to edit deeper values. >>> >>> https://github.com/grasmash/yaml-cli >>> yaml-cli update:value file.yml key value >>> >>> If you intend to keep developing yamlfukr >>> <https://github.com/golangdaddy/yamlfukr>, you might want to examine >>> some of the alternatives, and if you find them unsuitable, add to your >>> documentation why you find them so, so that someone coming on your project >>> can see why they should consider going with your tool instead of one of the >>> alternatives. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "golang-nuts" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to golang-nuts+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/golang-nuts/b1fb908a-94f7-4487-b76a-50153d87c868n%40googlegroups.com >>> <https://groups.google.com/d/msgid/golang-nuts/b1fb908a-94f7-4487-b76a-50153d87c868n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/CANaetAYF5USeu6OQivATC7TjciZfuCszK_-Lhok8ZxDsiBmWAw%40mail.gmail.com >> <https://groups.google.com/d/msgid/golang-nuts/CANaetAYF5USeu6OQivATC7TjciZfuCszK_-Lhok8ZxDsiBmWAw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CANaetAZcaAA9wJHkPuoO4adVd438L_vYH7PaVK%2B3Rg87%3DjNp1Q%40mail.gmail.com.
