You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*Note: in the future we may replace this with a YAML `!jwt` macro, and pass in the just the signing key as an environment variable.*
51
-
52
51
## Usage
53
52
54
53
### Running Mock Data Generation
@@ -58,14 +57,16 @@ Use uv to run the mock data tool (uv will automatically manage Python versions a
58
57
```bash
59
58
# Test the script (uv will create the virtual environment automatically).
60
59
uv run lfx-v2-mockdata --help
60
+
61
61
# Load some data!
62
-
uv run lfx-v2-mockdata -t playbooks/projects/{root_project_access,base_projects,extra_projects} playbooks/committees/base_committees
62
+
uv run lfx-v2-mockdata --jwt-rsa-secret "$JWT_RSA_SECRET" -t playbooks/projects/{root_project_access,base_projects,extra_projects} playbooks/committees/base_committees
63
63
```
64
64
65
65
**Important Notes:**
66
66
-**Order matters!** Playbook directories run in the order specified on the command line.
67
67
- Within each directory, playbooks execute in alphabetical order.
68
68
- Dependencies between playbooks should be considered when organizing execution order. Multiple passes are made to allow `!ref` calls to be resolved, but the right order will improve performance and help avoid max-retry errors.
69
+
- The `!jwt` macro will attempt to detect the JWKS key ID from the endpoint at `http://lfx-platform-heimdall.lfx.svc.cluster.local:4457/.well-known/jwks`. If this URL is not accessible from the execution environment, you must pass an explicit JWT key ID using the `--jwt-key-id` argument.
0 commit comments