zef VS Sparrow6

To begin, you'll want to make sure that you have Raku installed, I recommend using Rakubrew. Then we'll want to install Zef, if you're new to Raku, Zef is basically just NPM or CPAN for Raku, it's written by the fabulous Ugexe and is the default package manager people use with Raku. If you installed Raku with Rakubrew, you can simply run rakubrew build-zef and it will handle all of the configuration for you.

I tested it on my computer. I needed to install zef from here. I installed libraries needed to use rakudo_debug. Here hat I get below:

See: https://github.com/ugexe/zef/blob/9779091b7997468257ce3037f8bc0e9c65d1f974/t/repository.rakutest#L85-L128 for an example of how the tiering of ecosystems work, and https://github.com/ugexe/zef/commit/a12d286312c6d7bc3c8ffebe51cce4caae6268cf for some reasoning

I have Rakudo 2022.07 on my Mac. I cloned https://github.com/ugexe/zef, which got me version 0.14.4. I cd'ed into the clone and ran this:

zef -v install https://github.com/ugexe/zef.git

FROM ghcr.io/jj/raku-gha ENV PKGS="git tar" PKGS_TMP="make gcc linux-headers musl-dev" WORKDIR="/home/raku" LABEL version="1.0.3" maintainer="[email protected]" rakuversion=$VER USER root RUN apk update && apk upgrade && apk add --no-cache $PKGS $PKGS_TMP USER raku # Environment ENV PATH="${WORKDIR}/.raku/bin:${WORKDIR}/.raku/share/perl6/site/bin:${PATH}" \ ENV="${WORKDIR}/.profile"\ RAKULIB="inst#/home/raku/.raku" # Basic setup, programs and init WORKDIR $WORKDIR RUN git clone --depth 1 https://github.com/ugexe/zef.git \ && cd zef && raku -I. bin/zef install . \ && zef install Linenoise \ && cd .. && rm -rf zef USER root RUN apk del $PGKS_TMP USER raku ENTRYPOINT ["raku"]

This is the issue I found on GitHub.

Please pay attention if you want to dig really deep )) , then underlying SparrowCI itself is just a transpiler from YAML ( plus some more features ) into Sparrow DSL which is documented here - https://github.com/melezhik/sparrow6 but you probably don’t need that part if you are only interested in writing pipelines …

As an addition to what's been already said, you might distribute your personal libraries as Sparrow plugins and spin up a private Sparrow repo for that - https://github.com/melezhik/Sparrow6/blob/master/documentation/repository.md , it should not be very hard and by they way Sparrow is well integrated with zen by using Rakufile mechanism - https://github.com/melezhik/Sparrow6/blob/master/documentation/development.md#package-managers , so one can distribute any ref modules (including taken from git , not eco system ) by just including Rakufile into one's plugin ...

I think alternatives to Ansible such as Rex and Sparrow have "fake it and show me the commands" modes — but I'm not 100% sure.

I'm not sure if there is a full fledged web framework for Raku just yet, but one of its claims to fame is Sparrow. It's declarative configuration management akin to Puppet, Chef, or Ansible.

Sparrow an automation framework, and its modules

During this stage Bird will use prepared task checks rules (check file - /root/.bird/285892/state.check]) and run them against the output. Bird will use Sparrow task check DSL to do so.

1) Sparrow - https://github.com/melezhik/Sparrow6 Raku Automation Framework ( alternative to ansible )

Sparrow is a wonderful tool to automate @daily devops tasks. Recently I've dropped a new plugin called k8s-deployment-check to verify k8s deployments. It lets you with a little bit of Raku code effectively test entire k8s infrastructure, including k8s deployments.

Could be added pretty easily, Sparrow has cpan-package primitive for for that.