4 ms·

There are a million different tools that are designed to do this, e.g. this task (log into a bunch of machines and execute a specific command without any additi

There are a million different tools that are designed to do this, e.g. this task (log into a bunch of machines and execute a specific command without any additional tools running on each node) is literally the design use case for Ansible. It would be a simple playbook, why are you bringing AI into this at all?

giobox 1y ago
Agreed, this is truly bizarre to me. Is OP not going to have to do this work all over again in x days time once the nodes fill with stale docker assets again? AI can still be helpful here if new to scheduling a simple shell command, but I'd be asking the AI how do I automate the task away, not manually asking the AI to do the thing every time, or using my runners in a fashion that means I don't have to even concern myself with scheduled prune command calls.
- bdangubic 1y ago
  > but I'd be asking the AI how do I automate the task away AI said “I got this” :)
- almosthere 1y ago
  No, we have a team dedicated to fixing this long term, but this allowed 20 engineers to get working right away. Long term fix is now in.
  - giobox 1y ago
    If a team of 20 engineers got blocked because you/the team didn't run docker prune, you arguably have even bigger problems...
ericmcer 1y ago
Yeah that sounds like a CI/CD task or scheduled job. I would not want the AI to "rewrite" the scripts before running them. I can't really think of why I would want it to?
almosthere 1y ago
Because I didn't have to do anything other than write that english statement and it worked. Saved me a long time.
- mandevil 1y ago
  I'm glad this worked for you, but if it were me at most I would have asked Claude Code to write me an Ansible playbook for doing this, then run it myself. That gives me more flexibility to run this in the future, to change the commands, to try it, see that it fails, and do it again, etc. And I honestly am a little concerned about a private key for a major cloud account where Claude can use it, just because I'm more than a little paranoid about certs.
  - cowboy_henk 1y ago
    You're right to be concerned. OPs method is how you get pwned through prompt injection.

giobox 1y ago

Agreed, this is truly bizarre to me. Is OP not going to have to do this work all over again in x days time once the nodes fill with stale docker assets again? AI can still be helpful here if new to scheduling a simple shell command, but I'd be asking the AI how do I automate the task away, not manually asking the AI to do the thing every time, or using my runners in a fashion that means I don't have to even concern myself with scheduled prune command calls.

bdangubic 1y ago
> but I'd be asking the AI how do I automate the task away AI said “I got this” :)
almosthere 1y ago
No, we have a team dedicated to fixing this long term, but this allowed 20 engineers to get working right away. Long term fix is now in.
- giobox 1y ago
  If a team of 20 engineers got blocked because you/the team didn't run docker prune, you arguably have even bigger problems...

ericmcer 1y ago

Yeah that sounds like a CI/CD task or scheduled job. I would not want the AI to "rewrite" the scripts before running them. I can't really think of why I would want it to?

almosthere 1y ago

Because I didn't have to do anything other than write that english statement and it worked. Saved me a long time.

mandevil 1y ago
I'm glad this worked for you, but if it were me at most I would have asked Claude Code to write me an Ansible playbook for doing this, then run it myself. That gives me more flexibility to run this in the future, to change the commands, to try it, see that it fails, and do it again, etc. And I honestly am a little concerned about a private key for a major cloud account where Claude can use it, just because I'm more than a little paranoid about certs.
- cowboy_henk 1y ago
  You're right to be concerned. OPs method is how you get pwned through prompt injection.