Skip to content

Commit 3b034c6

Browse files
committed
feat: add initial files
0 parents  commit 3b034c6

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

53 files changed

+21805
-0
lines changed

.env.example

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# Minimum log level for console output.
2+
# Options: NOTSET, DEBUG, INFO, WARNING, ERROR, CRITICAL
3+
LOG_LEVEL="INFO"
4+
5+
# Enable logging to a file.
6+
# Options: true, false
7+
LOG_FILE_ENABLED="false"
8+
9+
# Path to the log file (used only if LOG_FILE_ENABLED=true).
10+
# Ensure the directory exists and the server has write permissions.
11+
LOG_FILE_PATH="./mcp-server.log"
12+
13+
# Minimum log level for file output (used only if LOG_FILE_ENABLED=true).
14+
# Options: NOTSET, DEBUG, INFO, WARNING, ERROR, CRITICAL
15+
LOG_FILE_LEVEL="DEBUG"
16+
17+
18+
# --- Service Configuration ---
19+
# Variables required for the MCP server's tools and resources.
20+
21+
# GitHub Personal Access Token (PAT)
22+
# Used by the 'terragrunt-issues' service to access GitHub API (e.g., search Terragrunt issues).
23+
# Required scope(s): TBD (e.g., public_repo if only accessing public data)
24+
# Generate a token here: https://github.com/settings/tokens
25+
GITHUB_TOKEN="ghp_YOUR_GITHUB_PAT_HERE"

.gitattributes

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Auto-detect text files and ensure LF line endings are used in the repo
2+
* text=auto eol=lf

.github/CODEOWNERS

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# CODEOWNERS file indicates code owners for certain files
2+
#
3+
# Code owners will automatically be added as a reviewer for PRs that touch
4+
# the owned files.
5+
#
6+
7+
# Default owners for everything in the repo
8+
#
9+
# Unless a later match takes precedence, these owners will be requested for
10+
# review when someone opens a pull request.
11+
12+
* @Excoriate
Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
---
2+
name: 🐞 Bug Report
3+
about: Create a detailed bug report to help improve the MCP Server
4+
title: "bug: "
5+
labels: ["bug"]
6+
assignees: ["Excoriate"] # Adjust if needed
7+
---
8+
9+
## 🔍 Bug Description
10+
11+
> [!WARNING]
12+
> Provide a clear and concise description of the bug you encountered with the
13+
> MCP server.
14+
15+
### Expected Behavior
16+
17+
> [!NOTE]
18+
> Describe what you expected to happen:
19+
>
20+
> - What was the intended outcome when interacting with the server?
21+
> - How should the server have responded or behaved?
22+
23+
### Actual Behavior
24+
25+
> [!IMPORTANT]
26+
> Describe what actually happened:
27+
>
28+
> - What went wrong?
29+
> - What unexpected results, errors, or responses did you observe?
30+
31+
## 🔬 Steps to Reproduce
32+
33+
> [!TIP]
34+
> Provide detailed steps to reproduce the bug:
35+
36+
1. Start the server using `deno task dev` or relevant command...
37+
2. Connect using MCP client '....' (e.g., Claude Desktop, MCP Inspector)
38+
3. Send request / Perform action '....'
39+
4. Observe the error/unexpected behavior '....'
40+
41+
### Minimal Reproducible Example
42+
43+
> [!WARNING]
44+
> If applicable, include a minimal code snippet (TypeScript) or configuration
45+
> that demonstrates the issue:
46+
47+
```typescript
48+
// Your minimal reproducible TypeScript code snippet (if applicable)
49+
// or relevant configuration details
50+
```
51+
52+
## 🌍 Environment Details
53+
54+
> [!IMPORTANT]
55+
> Provide context about your environment:
56+
57+
- **Deno Version**: (e.g., `deno --version`)
58+
- **MCP SDK Version**: (from `deno.lock` or `deno.json`, e.g.,
59+
`npm:@modelcontextprotocol/[email protected]`)
60+
- **Operating System**: (e.g., macOS Sonoma 14.1, Windows 11, Ubuntu 22.04)
61+
- **MCP Client Used**: (e.g., Claude Desktop vX.Y.Z, MCP Inspector, Custom
62+
Client)
63+
- **Relevant `deno.json` / `deno.lock` sections**: (if applicable)
64+
65+
## 📋 Diagnostic Information
66+
67+
> [!TIP]
68+
> Include any relevant diagnostic information:
69+
70+
- Full error messages from the server console
71+
- Full error messages or unexpected responses from the MCP client
72+
- Screenshots of the error or unexpected behavior
73+
- Relevant logs (please ensure no sensitive data is included)
74+
75+
## 🖼️ Additional Context
76+
77+
> [!NOTE]
78+
> Add any other context about the problem:
79+
>
80+
> - When did you first notice this issue?
81+
> - Does it happen consistently or intermittently?
82+
> - Any recent changes (e.g., dependency updates, code changes) that might have
83+
> introduced the bug?
84+
85+
### Checklist
86+
87+
- [ ] I've checked existing issues for duplicates
88+
- [ ] I've provided a clear description of the bug
89+
- [ ] I've included steps to reproduce
90+
- [ ] I've shared relevant environment details
91+
- [ ] I've added diagnostic information (if applicable)
92+
93+
**Thank you for helping improve the `mcp-terraform-aws-provider-docs` server!** 🐛
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
name: 🚀 Feature Request
3+
about: Suggest an idea to improve the mcp-terragrunt-docs server
4+
title: "feat: "
5+
labels: ["feature"] # Changed from enhancement to match settings.yml
6+
assignees: ["Excoriate"] # Adjust if needed
7+
---
8+
9+
## 🌟 Feature Description
10+
11+
> [!TIP]
12+
> Provide a clear and concise description of the feature you're proposing for
13+
> the MCP server.
14+
15+
### Problem Statement
16+
17+
> [!NOTE]
18+
> Is your feature request related to a problem? Describe the pain point.
19+
>
20+
> Example: "I'm always frustrated when I cannot get X context from the
21+
> server..."
22+
23+
### Proposed Solution
24+
25+
> [!IMPORTANT]
26+
> Describe the solution you'd like to see implemented.
27+
>
28+
> - What specific functionality are you suggesting?
29+
> - How would this improve the server or its interactions?
30+
31+
## 🎯 Use Case and Value
32+
33+
> [!TIP]
34+
> Explain the specific use case and the value this feature would bring:
35+
36+
- How would this feature be used?
37+
- What benefits would it provide (e.g., better context, new capabilities,
38+
improved developer experience)?
39+
40+
## 🔍 Alternatives Considered
41+
42+
> [!NOTE]
43+
> Have you explored alternative solutions or workarounds?
44+
>
45+
> - Describe other approaches you've considered
46+
> - Why weren't they sufficient?
47+
48+
## 🖼️ Additional Context
49+
50+
> [!TIP]
51+
> Add any other context, screenshots, examples, or references that might help
52+
> explain the feature request.
53+
54+
### Checklist
55+
56+
- [ ] I've checked that a similar feature doesn't already exist in open/closed
57+
issues
58+
- [ ] I've provided a clear problem statement (if applicable)
59+
- [ ] I've described the proposed solution
60+
- [ ] I've explained the use case and value
61+
62+
**Thank you for helping improve the `mcp-terraform-aws-provider-docs` server!** 🎉

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
## 🎯 What
2+
3+
Provide a concise description of the changes:
4+
5+
- ❓ What changes have you made? (High-level overview)
6+
- 🎉 What does it mean to the user? (In plain English)
7+
8+
Example:
9+
10+
- 🚀 Added new MCP tool `get_terragrunt_config`.
11+
- 🎉 This allows clients to request specific Terragrunt configuration details
12+
via the MCP server.
13+
14+
## 🤔 Why
15+
16+
Explain why the changes are necessary:
17+
18+
- 💡 Why were these changes made?
19+
- 🎯 What's the benefit?
20+
21+
Example:
22+
23+
- 💡 This tool was added to provide necessary context for an AI agent analyzing
24+
Terragrunt setups.
25+
- 🎯 This enables more accurate and context-aware interactions related to
26+
Terragrunt documentation and state.
27+
28+
## 📚 References
29+
30+
Link any supporting context or documentation:
31+
32+
- 🔗 Github issues, documentation, helpful links.
33+
- ✅ Use `closes #123`, if this PR closes a GitHub issue `#123`

.github/auto-comment.yml

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
pullRequestOpened: |
3+
:wave: Thanks for creating a PR!
4+
5+
Before we can merge this PR, please make sure that all the following items have been
6+
checked off. If any of the checklist items are not applicable, please leave them but
7+
write a little note why.
8+
9+
- [ ] Wrote tests
10+
- [ ] Check the CONTRIBUTING guide for other ways to contribute
11+
- [ ] Linked to Github issue with discussion and accepted design OR link to spec that
12+
describes this work.
13+
- [ ] Updated relevant documentation (`docs/`) and code comments
14+
- [ ] Re-reviewed `Files changed` in the Github PR explorer
15+
- [ ] Applied Appropriate Labels
16+
17+
18+
Thank you for your contribution! :rocket:

.github/config.yml

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
3+
# Comment to be posted to on first time issues
4+
newIssueWelcomeComment: >
5+
Thanks for opening your first issue here! 👍 Be sure to follow the issue template. #magic___^_^___line
6+
# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
7+
# Comment to be posted to on PRs from first time contributors in your repository
8+
newPRWelcomeComment: >
9+
Thanks for opening this pull request! 👍 Please check out our contributing guidelines. #magic___^_^___line
10+
# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
11+
# Comment to be posted to on pull requests merged by a first time user
12+
firstPRMergeComment: >
13+
Congrats on merging your first pull request! 🎉 We here at `mcp-terraform-aws-provider-docs` are proud of you.

.github/labeler.yml

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# .github/labeler.yml - Config for actions/labeler action
2+
# Defines labels based on files modified in a PR
3+
4+
# Label for CI/CD changes
5+
ci/cd:
6+
- .github/workflows/*
7+
8+
# Label for documentation changes
9+
documentation:
10+
- README.md
11+
- docs/**/*.md # Updated path for all docs
12+
- "*.md" # Root level markdown files
13+
14+
# Label for source code changes
15+
source:
16+
- main.ts
17+
- "**/*.ts" # All TypeScript files
18+
19+
# Label for configuration changes / patches
20+
patch:
21+
- LICENSE
22+
- justfile # Added
23+
- deno.json # Added
24+
- deno.lock # Added
25+
- .github/labeler.yml
26+
- .github/settings.yml
27+
- .github/dependabot.yml # Keep if dependabot is used
28+
- .github/ISSUE_TEMPLATE/* # Added
29+
- .github/CODEOWNERS # Added
30+
- .github/*.yml # Other root .github YAML configs
31+
- .gitignore
32+
- .gitattributes

.github/no-response.yml

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
# Configuration for probot-no-response - https://github.com/probot/no-response
3+
4+
# Number of days of inactivity before an Issue is closed for lack of response
5+
daysUntilClose: 30
6+
# Label requiring a response
7+
responseRequiredLabel: more-information-needed
8+
# Comment to post when closing an Issue for lack of response. Set to `false` to disable
9+
closeComment: >-
10+
This issue has been automatically closed because there has been no response to our request for more information from the
11+
original author. With only the information that is currently in the issue, we don't have enough information to take action.
12+
Please feel free to reach out if you have or find the answers we need so that we can investigate further. Thank you!

0 commit comments

Comments
 (0)