Add Python implementation and playbooks #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Eric Searcy <[email protected]>
There was a problem hiding this comment.
Pull Request Overview
This PR introduces a new mock data generation tool for the LFX v2 platform. The tool uses YAML playbooks with Jinja2 templating to create test data through HTTP requests, NATS messaging, and KV store operations.
- Implements a playbook-based system supporting multiple workflow types (HTTP requests, NATS publish/request, NATS KV operations)
- Includes custom YAML tags (
!ref,!sub,!include) for dynamic data referencing and templating - Provides sample playbooks for populating projects, committees, and permissions
Reviewed Changes
Copilot reviewed 21 out of 23 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| uv.lock | Lockfile defining all dependencies including faker, nats-py, pydantic, jinja2 |
| src/lfx_v2_mockdata/init.py | Main script implementing playbook execution engine with JMESPath support |
| src/custom_logging/init.py | Structured logging configuration with JSON and console output |
| pyproject.toml | Project configuration with dependencies and tooling setup |
| README.md | Documentation for setup, usage, and playbook structure |
| playbooks/* | YAML playbooks defining data generation scenarios |
| scripts/mock-heimdall-jwt.sh | Helper script for generating authentication tokens |
| LICENSE* | MIT license for code, CC-BY-4.0 for documentation |
| .github/workflows/* | CI/CD workflows for linting and license checks |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Also remove the +x bit from the lfx_v2_mockdata script and remove its shebang line, since it's not intended to be executed directly. Signed-off-by: Eric Searcy <[email protected]>
Linting, vulnerabilities, etc. Signed-off-by: Eric Searcy <[email protected]>
Contributor
Author
|
gitleaks seems to be failing but it's seeing files in #1 |
The main reason for adding this was in order to exclude the "playbooks" folder, because yamllint cannot lint pre-rendered Jinja2 templates. Signed-off-by: Eric Searcy <[email protected]>
emsearcy
force-pushed
the
python-implementation
branch
from
541a602 to
a05f513
Compare
Signed-off-by: Eric Searcy <[email protected]>
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.