Skip to content

docs: Remove Splunk General Terms references from Helm deployment guide#76

Open
vivekr-splunk wants to merge 1 commit intomainfrom
fix-helm-docs-remove-sgt
Open

docs: Remove Splunk General Terms references from Helm deployment guide#76
vivekr-splunk wants to merge 1 commit intomainfrom
fix-helm-docs-remove-sgt

Conversation

@vivekr-splunk
Copy link
Collaborator

Summary

Removes all Splunk General Terms (SGT) references from the Helm deployment documentation to align with code changes that removed SGT validation from the Helm charts.

Changes Made

This PR updates docs/deployment/helm-deployment.md to remove:

  • All "IMPORTANT" warnings about accepting Splunk General Terms
  • Configuration examples with acceptGeneralTerms settings
  • Configuration examples with splunkGeneralTerms values
  • Notes referencing Splunk Operator README for SGT acceptance
  • Links to Splunk General Terms legal page
  • Comments like "# Accept Splunk General Terms (REQUIRED)"

What Remains

The documentation still provides:

  • ✅ Clean, straightforward installation instructions
  • ✅ All technical configuration examples
  • ✅ Complete chart architecture documentation
  • ✅ Troubleshooting guides
  • ✅ Building charts from source instructions

Why This Change?

The SGT references were removed from the codebase per legal requirements in previous commits. This PR ensures the documentation stays in sync with the actual implementation, providing users with accurate installation instructions without referencing removed functionality.

Testing

  • Documentation builds without errors
  • All installation examples are syntactically correct
  • No broken internal links
  • Examples align with actual chart structure

Related Issues

Follows up on earlier work that removed SGT validation from Helm charts per legal requirements.

🤖 Generated with Claude Code

Remove all references to Splunk General Terms (SGT) acceptance from the
Helm deployment documentation per legal requirements. This includes:
- All IMPORTANT warnings about accepting Splunk General Terms
- Configuration examples with acceptGeneralTerms settings
- Configuration examples with splunkGeneralTerms values
- Notes referencing Splunk Operator README for SGT acceptance
- Links to Splunk General Terms page

The documentation now provides clean, straightforward installation
instructions without SGT configuration requirements, aligning with
the code changes that removed SGT validation from the charts.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings December 20, 2025 07:01
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes all Splunk General Terms (SGT) references from the Helm deployment documentation to align with earlier code changes that removed SGT validation from the Helm charts per legal requirements. The documentation is updated to provide clean, straightforward installation instructions without referencing the removed functionality.

Key Changes:

  • Removed all "IMPORTANT" warnings and notes about accepting Splunk General Terms
  • Removed configuration examples containing acceptGeneralTerms and splunkGeneralTerms parameters
  • Removed links to Splunk General Terms legal page and Splunk Operator README references

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 20390830736

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 36.876%

Totals Coverage Status
Change from base Build 20390744785: 0.0%
Covered Lines: 2342
Relevant Lines: 6351

💛 - Coveralls

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.

2 participants