Skip to content

fix: do not add licence acceptance to compose files silently - #10

Merged
dd-Splunk merged 1 commit into
mainfrom
fix/accept-license-explicit
Oct 29, 2026
Merged

dd-Splunk merged 1 commit into
mainfrom
fix/accept-license-explicit

Conversation

@dd-Splunk

Copy link
Copy Markdown
Owner

Summary

  • SKILL.md Boundaries: licence/terms acceptance (SPLUNK_START_ARGS: --accept-license, SPLUNK_GENERAL_TERMS on 10.x) is the user's decision; leave the lines out unless they have said they accept, and say the container will not start without them.
  • references/docker-compose.md: the compose example now has those lines commented out, and the note matches the rule. Previously the example included them, which contradicted "do not add silently" and led simulated agents to add --accept-license.
  • evals.json: credentials_never_in_chat now fails if the compose file includes the acceptance lines without flagging them.

No version bump or changelog entry (skill text only); can be rolled into the next release.

Test plan

  • python3 -m unittest discover -s tests (149 tests, OK)
  • Simulated behaviour eval (one run, subagent following SKILL.md): password kept out, acceptance lines commented out and flagged
  • CI green

🤖 Generated with Claude Code

Make the rule explicit in SKILL.md, comment out the acceptance lines in the
compose example, and make the credentials eval fail when --accept-license or
the 10.x terms are added without flagging them as the user's decision.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@dd-Splunk
dd-Splunk merged commit 2b2b945 into main Oct 29, 2026
6 checks passed
@dd-Splunk
dd-Splunk deleted the fix/accept-license-explicit branch October 29, 2026 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant