On Sun, Jun 2, 2019 at 10:24 AM Shimin Guo <smguo2...@gmail.com> wrote:
> I think I should say more about my motivation. In my day-to-day work, we 
> often need to set up server hosts, and we use ansible to do that. There are 
> other tools like Chef, SaltStack, etc., that are all similar. With these 
> tools, instead of using shell commands, we can use commands that are 
> higher-level, more declarative, and idempotent, such as "path /a/b/c should 
> exist", "file xyz should have this content", "package foo should be 
> installed", etc. While definitely an improvement over shell scripting, they 
> still leave a lot to be desired. Specifically, I'd like to be able to
> - reason about the state of the system after a sequence of commands are run, 
> and
> - state formally what a sequence of commands should accomplish.

I also use Ansible in my daily work and have desired a more type safe
way of handling deployment, etc. I'm very interested in seeing what
you come up with. I ended up exploring a more prolog-like solution,
but would still like to see what's possible in the typed world. I went
for prolog to solve the problem of "Here is system in state A", "here
is my target state, B", search for the optimal commands to run that
take the system from A to B.

An approach I was considering doing was having an ATS program generate
an ansible playbook when run. So instead of writing error prone
Ansible/Python, write ATS which checks the types like your examples,
and when run it produces the Ansible playbook.

-- 
http://bluishcoder.co.nz

-- 
You received this message because you are subscribed to the Google Groups 
"ats-lang-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ats-lang-users+unsubscr...@googlegroups.com.
To post to this group, send email to ats-lang-users@googlegroups.com.
Visit this group at https://groups.google.com/group/ats-lang-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ats-lang-users/CALn1vHFgf83RgKYTDfBvNzt217zcOqN99cwAQPTtOrqJce-%3Dnw%40mail.gmail.com.

Reply via email to