entropy-data 0.3.18__tar.gz → 0.3.20__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (90) hide show
  1. {entropy_data-0.3.18 → entropy_data-0.3.20}/.dockerignore +2 -1
  2. {entropy_data-0.3.18 → entropy_data-0.3.20}/.github/workflows/ci.yaml +32 -9
  3. {entropy_data-0.3.18 → entropy_data-0.3.20}/.github/workflows/release.yaml +42 -14
  4. {entropy_data-0.3.18 → entropy_data-0.3.20}/.pre-commit-config.yaml +1 -1
  5. {entropy_data-0.3.18 → entropy_data-0.3.20}/CHANGELOG.md +17 -1
  6. {entropy_data-0.3.18 → entropy_data-0.3.20}/Dockerfile +2 -2
  7. entropy_data-0.3.20/PKG-INFO +315 -0
  8. {entropy_data-0.3.18 → entropy_data-0.3.20}/README.md +94 -1
  9. entropy_data-0.3.20/docs/apply-command-plan.md +256 -0
  10. {entropy_data-0.3.18 → entropy_data-0.3.20}/pyproject.toml +26 -4
  11. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/cli.py +37 -1
  12. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/client.py +17 -0
  13. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/datacontracts.py +1 -1
  14. entropy_data-0.3.20/src/entropy_data/commands/import_export.py +165 -0
  15. entropy_data-0.3.20/src/entropy_data/commands/schemas.py +54 -0
  16. entropy_data-0.3.20/src/entropy_data/commands/sync.py +101 -0
  17. entropy_data-0.3.20/src/entropy_data/resources.py +166 -0
  18. entropy_data-0.3.20/src/entropy_data/sync.py +566 -0
  19. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_datacontracts.py +2 -2
  20. entropy_data-0.3.20/tests/commands/test_import_export.py +647 -0
  21. entropy_data-0.3.20/tests/commands/test_schemas.py +127 -0
  22. entropy_data-0.3.18/PKG-INFO +0 -24
  23. entropy_data-0.3.18/src/entropy_data/commands/import_export.py +0 -135
  24. {entropy_data-0.3.18 → entropy_data-0.3.20}/.editorconfig +0 -0
  25. {entropy_data-0.3.18 → entropy_data-0.3.20}/.github/dependabot.yml +0 -0
  26. {entropy_data-0.3.18 → entropy_data-0.3.20}/.github/pull_request_template.md +0 -0
  27. {entropy_data-0.3.18 → entropy_data-0.3.20}/.gitignore +0 -0
  28. {entropy_data-0.3.18 → entropy_data-0.3.20}/CLAUDE.md +0 -0
  29. {entropy_data-0.3.18 → entropy_data-0.3.20}/LICENSE +0 -0
  30. {entropy_data-0.3.18 → entropy_data-0.3.20}/release +0 -0
  31. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/__init__.py +0 -0
  32. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/__main__.py +0 -0
  33. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/__init__.py +0 -0
  34. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/access.py +0 -0
  35. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/api_keys.py +0 -0
  36. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/assets.py +0 -0
  37. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/certifications.py +0 -0
  38. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/classifications.py +0 -0
  39. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/connection.py +0 -0
  40. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/connectors.py +0 -0
  41. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/costs.py +0 -0
  42. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/dataproducts.py +0 -0
  43. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/definitions.py +0 -0
  44. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/events.py +0 -0
  45. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/example_data.py +0 -0
  46. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/git_credentials.py +0 -0
  47. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/gitconnections.py +0 -0
  48. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/integrations.py +0 -0
  49. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/lineage.py +0 -0
  50. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/notification_channels.py +0 -0
  51. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/organization.py +0 -0
  52. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/policies.py +0 -0
  53. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/search.py +0 -0
  54. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/semantics.py +0 -0
  55. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/settings.py +0 -0
  56. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/sourcesystems.py +0 -0
  57. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/tags.py +0 -0
  58. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/teams.py +0 -0
  59. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/test_results.py +0 -0
  60. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/commands/usage.py +0 -0
  61. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/config.py +0 -0
  62. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/output.py +0 -0
  63. {entropy_data-0.3.18 → entropy_data-0.3.20}/src/entropy_data/util.py +0 -0
  64. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/__init__.py +0 -0
  65. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/__init__.py +0 -0
  66. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_access_request.py +0 -0
  67. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_api_keys.py +0 -0
  68. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_assets.py +0 -0
  69. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_classifications.py +0 -0
  70. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_connection.py +0 -0
  71. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_connectors.py +0 -0
  72. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_costs.py +0 -0
  73. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_dataproducts.py +0 -0
  74. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_git_credentials.py +0 -0
  75. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_gitconnections.py +0 -0
  76. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_integrations.py +0 -0
  77. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_lineage.py +0 -0
  78. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_notification_channels.py +0 -0
  79. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_organization.py +0 -0
  80. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_policies.py +0 -0
  81. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_semantics.py +0 -0
  82. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_settings.py +0 -0
  83. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_tags.py +0 -0
  84. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_team_roles.py +0 -0
  85. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_teams.py +0 -0
  86. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/commands/test_usage.py +0 -0
  87. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/conftest.py +0 -0
  88. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/test_cli.py +0 -0
  89. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/test_client.py +0 -0
  90. {entropy_data-0.3.18 → entropy_data-0.3.20}/tests/test_config.py +0 -0
@@ -15,7 +15,8 @@ tests/
15
15
  .editorconfig
16
16
 
17
17
  # Docs & project meta
18
- README.md
18
+ # README.md is not ignored: pyproject.toml declares it as the project readme,
19
+ # so the build backend needs it present to install the package.
19
20
  CHANGELOG.md
20
21
  CLAUDE.md
21
22
  LICENSE
@@ -20,11 +20,13 @@ jobs:
20
20
  - '3.11'
21
21
  - '3.12'
22
22
  - '3.13'
23
+ - '3.14'
23
24
  fail-fast: false
24
25
  steps:
25
- - uses: actions/checkout@v4
26
+ - uses: actions/checkout@v7
26
27
  - name: Install uv
27
- uses: astral-sh/setup-uv@v5
28
+ # setup-uv no longer publishes floating major tags, so pin the exact version.
29
+ uses: astral-sh/setup-uv@v9.0.0
28
30
  with:
29
31
  python-version: ${{ matrix.python-version }}
30
32
  - name: Install the project
@@ -42,9 +44,9 @@ jobs:
42
44
  - '3.12'
43
45
  fail-fast: false
44
46
  steps:
45
- - uses: actions/checkout@v4
47
+ - uses: actions/checkout@v7
46
48
  - name: Install uv
47
- uses: astral-sh/setup-uv@v5
49
+ uses: astral-sh/setup-uv@v9.0.0
48
50
  with:
49
51
  python-version: ${{ matrix.python-version }}
50
52
  - name: Install the project
@@ -59,12 +61,15 @@ jobs:
59
61
  needs:
60
62
  - test
61
63
  if: github.event_name != 'pull_request' && github.repository == 'entropy-data/entropy-data-cli'
64
+ permissions:
65
+ contents: read
66
+ id-token: write # Mint the OIDC token that keyless cosign signing exchanges for a Fulcio certificate.
62
67
  steps:
63
68
  - name: Checkout
64
- uses: actions/checkout@v4
69
+ uses: actions/checkout@v7
65
70
  - name: Docker meta
66
71
  id: meta
67
- uses: docker/metadata-action@v5
72
+ uses: docker/metadata-action@v6
68
73
  with:
69
74
  images: |
70
75
  entropydata/entropy-data-cli
@@ -74,14 +79,15 @@ jobs:
74
79
  type=semver,pattern={{version}}
75
80
  type=semver,pattern={{major}}.{{minor}}
76
81
  - name: Set up Docker Buildx
77
- uses: docker/setup-buildx-action@v3
82
+ uses: docker/setup-buildx-action@v4
78
83
  - name: Login to Docker Hub
79
- uses: docker/login-action@v3
84
+ uses: docker/login-action@v4
80
85
  with:
81
86
  username: ${{ secrets.DOCKERHUB_USERNAME }}
82
87
  password: ${{ secrets.DOCKERHUB_TOKEN }}
83
88
  - name: Build and push
84
- uses: docker/build-push-action@v5
89
+ id: build
90
+ uses: docker/build-push-action@v7
85
91
  with:
86
92
  context: .
87
93
  platforms: linux/amd64,linux/arm64
@@ -89,3 +95,20 @@ jobs:
89
95
  tags: entropydata/entropy-data-cli:snapshot-latest
90
96
  labels: ${{ steps.meta.outputs.labels }}
91
97
  sbom: true
98
+ provenance: mode=max
99
+
100
+ # cosign-installer publishes no floating major tag, so this must name an
101
+ # exact version.
102
+ - uses: sigstore/cosign-installer@v4.1.2
103
+ if: github.ref == 'refs/heads/main'
104
+
105
+ # Sign the index digest rather than a tag: the index commits to the
106
+ # platform manifests and the SBOM/provenance attestations, so one
107
+ # signature covers all of them, and the binding cannot be moved by
108
+ # retagging. Only reachable when the image was actually pushed — the
109
+ # release workflow calls this workflow on a tag, where push is false.
110
+ - name: Sign image
111
+ if: github.ref == 'refs/heads/main'
112
+ env:
113
+ DIGEST: ${{ steps.build.outputs.digest }}
114
+ run: cosign sign --yes "entropydata/entropy-data-cli@${DIGEST}"
@@ -9,12 +9,22 @@ name: Release
9
9
  jobs:
10
10
  test:
11
11
  uses: ./.github/workflows/ci.yaml
12
+ # A called workflow cannot be granted more than its caller holds, and the
13
+ # workflow-level default above is `contents: read`. ci.yaml's `docker` job
14
+ # requests `id-token: write` for keyless cosign signing, so without this the
15
+ # whole run fails at startup before any job executes — permissions are
16
+ # validated up front, regardless of the `if:` conditions that would actually
17
+ # skip the signing steps on a tag. Granted on this job only, not raised to
18
+ # the workflow level.
19
+ permissions:
20
+ contents: read
21
+ id-token: write
12
22
  secrets: inherit
13
23
 
14
24
  check_version:
15
25
  runs-on: ubuntu-latest
16
26
  steps:
17
- - uses: actions/checkout@v4
27
+ - uses: actions/checkout@v7
18
28
  - name: check tag version == pyproject.version
19
29
  id: version
20
30
  run: |
@@ -52,17 +62,17 @@ jobs:
52
62
  - test
53
63
  - check_version
54
64
  steps:
55
- - uses: actions/checkout@v4
65
+ - uses: actions/checkout@v7
56
66
  with:
57
67
  fetch-depth: 0
58
68
  - name: Install uv
59
- uses: astral-sh/setup-uv@v5
69
+ uses: astral-sh/setup-uv@v9.0.0
60
70
  with:
61
71
  python-version: "3.12"
62
72
  - name: Build package
63
73
  run: uv build
64
74
  - name: Store the distribution packages
65
- uses: actions/upload-artifact@v4
75
+ uses: actions/upload-artifact@v7
66
76
  with:
67
77
  name: python-package-distributions
68
78
  path: dist/
@@ -80,7 +90,7 @@ jobs:
80
90
  id-token: write
81
91
  steps:
82
92
  - name: Download all the dists
83
- uses: actions/download-artifact@v4
93
+ uses: actions/download-artifact@v8
84
94
  with:
85
95
  name: python-package-distributions
86
96
  path: dist/
@@ -97,7 +107,7 @@ jobs:
97
107
  contents: write
98
108
  id-token: write
99
109
  steps:
100
- - uses: actions/checkout@v4
110
+ - uses: actions/checkout@v7
101
111
  - name: Extract changelog for version
102
112
  run: |
103
113
  VERSION="${{ github.ref_name }}"
@@ -105,12 +115,12 @@ jobs:
105
115
  sed -n "/^## \[$VERSION\]/,/^## \[/p" CHANGELOG.md | head -n -1 > release_notes.md
106
116
  cat release_notes.md
107
117
  - name: Download all the dists
108
- uses: actions/download-artifact@v4
118
+ uses: actions/download-artifact@v8
109
119
  with:
110
120
  name: python-package-distributions
111
121
  path: dist/
112
122
  - name: Sign the dists with Sigstore
113
- uses: sigstore/gh-action-sigstore-python@v3.0.0
123
+ uses: sigstore/gh-action-sigstore-python@v3.4.0
114
124
  with:
115
125
  inputs: >-
116
126
  ./dist/*.tar.gz
@@ -136,12 +146,15 @@ jobs:
136
146
  needs:
137
147
  - test
138
148
  - check_version
149
+ permissions:
150
+ contents: read
151
+ id-token: write # Mint the OIDC token that keyless cosign signing exchanges for a Fulcio certificate.
139
152
  steps:
140
153
  - name: Checkout
141
- uses: actions/checkout@v4
154
+ uses: actions/checkout@v7
142
155
  - name: Docker meta
143
156
  id: meta
144
- uses: docker/metadata-action@v5
157
+ uses: docker/metadata-action@v6
145
158
  with:
146
159
  images: |
147
160
  entropydata/entropy-data-cli
@@ -151,14 +164,15 @@ jobs:
151
164
  type=semver,pattern={{version}}
152
165
  type=semver,pattern={{major}}.{{minor}}
153
166
  - name: Set up Docker Buildx
154
- uses: docker/setup-buildx-action@v3
167
+ uses: docker/setup-buildx-action@v4
155
168
  - name: Login to Docker Hub
156
- uses: docker/login-action@v3
169
+ uses: docker/login-action@v4
157
170
  with:
158
171
  username: ${{ secrets.DOCKERHUB_USERNAME }}
159
172
  password: ${{ secrets.DOCKERHUB_TOKEN }}
160
173
  - name: Build and push
161
- uses: docker/build-push-action@v5
174
+ id: build
175
+ uses: docker/build-push-action@v7
162
176
  with:
163
177
  context: .
164
178
  platforms: linux/amd64,linux/arm64
@@ -166,6 +180,20 @@ jobs:
166
180
  tags: ${{ steps.meta.outputs.tags }}
167
181
  labels: ${{ steps.meta.outputs.labels }}
168
182
  sbom: true
183
+ provenance: mode=max
184
+
185
+ # cosign-installer publishes no floating major tag, so this must name an
186
+ # exact version.
187
+ - uses: sigstore/cosign-installer@v4.1.2
188
+
189
+ # Sign the index digest rather than a tag: the index commits to the
190
+ # platform manifests and the SBOM/provenance attestations, so one
191
+ # signature covers all of them, and the binding cannot be moved by
192
+ # retagging.
193
+ - name: Sign image
194
+ env:
195
+ DIGEST: ${{ steps.build.outputs.digest }}
196
+ run: cosign sign --yes "entropydata/entropy-data-cli@${DIGEST}"
169
197
 
170
198
  publish-to-testpypi:
171
199
  name: Publish Python distribution to TestPyPI
@@ -179,7 +207,7 @@ jobs:
179
207
  id-token: write
180
208
  steps:
181
209
  - name: Download all the dists
182
- uses: actions/download-artifact@v4
210
+ uses: actions/download-artifact@v8
183
211
  with:
184
212
  name: python-package-distributions
185
213
  path: dist/
@@ -1,6 +1,6 @@
1
1
  repos:
2
2
  - repo: https://github.com/astral-sh/ruff-pre-commit
3
- rev: v0.14.3
3
+ rev: v0.15.22
4
4
  hooks:
5
5
  - id: ruff
6
6
  args: [ --fix ]
@@ -1,6 +1,22 @@
1
1
  # Changelog
2
2
 
3
- ## [Unreleased]
3
+ ## [0.3.20]
4
+
5
+ - Support Python 3.14, now covered by the CI test matrix alongside 3.11, 3.12, and 3.13.
6
+ - Publish keywords and `Issues`/`Changelog` links in the PyPI package metadata so the project is findable and its sidebar links to the tracker and the changelog.
7
+ - Add `entropy-data export dir <path>` to enumerate an organization's portable state into a local YAML tree (one directory per resource, one file per resource named by its id), mirroring the app's organization-export layout so the artifacts interchange.
8
+ - Add `entropy-data apply dir <path>` to reconcile a local export directory tree into the connected instance, in the spirit of `kubectl apply -f <dir>`. The tree uses a folder-as-kind convention: the directory name is the resource kind and each YAML file below it is one resource (addressed by the id in its body); folders that are not a known kind are ignored. By default the whole tree is applied; `--include`/`--exclude` narrow it, `--dry-run` previews, and `--prune` also deletes instance resources absent from the tree (reverse dependency order, confirmation-gated unless `--yes`). `import zip` (unchanged) now extracts to a temp directory and applies it through the same engine.
9
+ - Add `entropy-data sync --source <conn> --target <conn> --include <resources>` to copy portable organization state from one connection to another by exporting the source into a staged directory and importing it into the target. `sync` copies **nothing by default** — the resources to copy must be named with `--include`, and a run without it fails with a non-zero exit and the list of known resources. Supports `--exclude`, `--prune`, `--dry-run` (per-resource create/update/prune counts), and `--keep <dir>` to retain the staged export. Supported resources: `teams`, `tags`, `definitions`, `policies`, `sourcesystems`, `certifications`, `classification-schemes`, `assets`, `datacontracts`, `dataproducts`, `example-data`, `access`, `semantic-namespaces`, `semantic-ontology`, `organization-features`. Not synced: users & team members, API keys, git credentials, integration/connector credentials, usage, costs, test results, events, and lineage; organization customization, SCIM mapping, team-roles config, notification channels, connectors, and integrations are not supported yet. See the [Sync Environments guide](https://docs.entropy-data.com/howto/import-export) for a walkthrough.
10
+ - Fix `apply`/`import` silently dropping `sourcesystems/` from an organization export — source systems are now applied in their correct dependency position (after policies, before assets).
11
+ - `export`/`apply`/`sync` now also copy `certifications`, `classification-schemes`, `example-data`, and the `semantics` graph. All writes are idempotent PUT-by-id, team members are stripped on apply, asset tag assignments are replayed, and audit fields are stripped before PUT.
12
+ - The `semantics` graph is copied as one OSI-compliant ontology YAML document per namespace (`semantic-ontology/<namespace>.yaml`) via the app's `GET`/`PUT /api/semantics/experimental/namespaces/{ns}/ontology.yaml` endpoint, which imports it in the correct internal order (groups before members, concepts before relationships) and provisions the namespace from the metadata (`display_name`, `read_only`, `owner`) carried in the document's root `custom_properties`. There is no separate namespace artifact; a tree from an older version that still carries a `semantic-namespaces/` folder is applied as before. Requires that endpoint on the target instance.
13
+ - `export`/`apply`/`sync` copy the organization's feature configuration as a singleton (`GET`/`PUT /api/organization/features`, artifact `organization-features/organization-features.yaml`), applied last so a restrictive policy it carries cannot reject earlier imports. Requires the app-side endpoint (entropy-data#1521); singletons are never pruned.
14
+ - Update dependencies to their latest versions to clear all open security advisories: `urllib3` 2.7.0 (cross-origin header forwarding on proxied redirects, decompression-bomb bypass), `requests` 2.34.2 (insecure temp file reuse in `extract_zipped_paths()`), `idna` 3.18 (`idna.encode()` bypass of the CVE-2024-3651 fix), `pygments` 2.20.0 (ReDoS in GUID matching), and `pytest` 9.1.1 (vulnerable tmpdir handling). The minimum `requests` is now 2.33 so installs from PyPI also get the fix.
15
+
16
+ ## [0.3.19]
17
+
18
+ - Fix `entropy-data datacontracts yaml <id>` requesting `/api/datacontracts/{id}.yaml`, which does not exist on the server, resulting in a 404. It now requests the documented `/api/datacontracts/{id}/datacontract.yaml`.
19
+ - Add `entropy-data schemas get odcs|odps` to fetch the JSON Schemas that data contracts (ODCS) and data products (ODPS) validate against (`GET /api/schemas/{odcs|odps}[-<version>][-custom].schema.json`). By default the current base schema is printed to stdout; `--custom` composes the organization's customization overlay onto the base schema via `allOf` (the schema the data contract editor validates against), `--version` pins a specification version, and `--file` writes to a file, reporting the served base version from the `X-Schema-Version` header.
4
20
 
5
21
  ## [0.3.18]
6
22
 
@@ -3,9 +3,9 @@ FROM python:3.12-slim
3
3
  ENV PYTHONUNBUFFERED=1
4
4
  ENV UV_COMPILE_BYTECODE=1
5
5
 
6
- COPY --from=ghcr.io/astral-sh/uv:0.7.12 /uv /uvx /bin/
6
+ COPY --from=ghcr.io/astral-sh/uv:0.11.29 /uv /uvx /bin/
7
7
 
8
- COPY pyproject.toml uv.lock /app/
8
+ COPY pyproject.toml uv.lock README.md /app/
9
9
  COPY src/ /app/src/
10
10
 
11
11
  RUN cd /app && uv pip --no-cache-dir install --system .
@@ -0,0 +1,315 @@
1
+ Metadata-Version: 2.4
2
+ Name: entropy-data
3
+ Version: 0.3.20
4
+ Summary: CLI for Entropy Data
5
+ Project-URL: Homepage, https://entropy-data.com
6
+ Project-URL: Documentation, https://docs.entropy-data.com
7
+ Project-URL: Repository, https://github.com/entropy-data/entropy-data-cli
8
+ Project-URL: Issues, https://github.com/entropy-data/entropy-data-cli/issues
9
+ Project-URL: Changelog, https://github.com/entropy-data/entropy-data-cli/blob/main/CHANGELOG.md
10
+ Author-email: Entropy Data <support@entropy-data.com>
11
+ License-Expression: MIT
12
+ License-File: LICENSE
13
+ Keywords: cli,data-catalog,data-contract,data-governance,data-marketplace,data-mesh,data-product,entropy-data,odcs,odps
14
+ Classifier: Programming Language :: Python :: 3.11
15
+ Classifier: Programming Language :: Python :: 3.12
16
+ Classifier: Programming Language :: Python :: 3.13
17
+ Classifier: Programming Language :: Python :: 3.14
18
+ Requires-Python: >=3.11
19
+ Requires-Dist: pydantic<3.0,>=2.10
20
+ Requires-Dist: python-dotenv<2.0,>=1.0
21
+ Requires-Dist: pyyaml<7.0,>=6.0
22
+ Requires-Dist: requests<3.0,>=2.33
23
+ Requires-Dist: rich<16.0,>=14.0
24
+ Requires-Dist: tomli-w<2.0,>=1.0
25
+ Requires-Dist: truststore<1.0,>=0.10
26
+ Requires-Dist: typer<1.0,>=0.15.0
27
+ Provides-Extra: dev
28
+ Requires-Dist: pre-commit>=3.7; extra == 'dev'
29
+ Requires-Dist: pytest>=9.0.3; extra == 'dev'
30
+ Requires-Dist: responses>=0.25; extra == 'dev'
31
+ Requires-Dist: ruff<0.16,>=0.8; extra == 'dev'
32
+ Description-Content-Type: text/markdown
33
+
34
+ # Entropy Data CLI
35
+
36
+ <p>
37
+ <a href="https://github.com/entropy-data/entropy-data-cli/actions/workflows/ci.yaml?query=branch%3Amain">
38
+ <img alt="CI" src="https://img.shields.io/github/actions/workflow/status/entropy-data/entropy-data-cli/ci.yaml?branch=main"></a>
39
+ <a href="https://pypi.org/project/entropy-data/">
40
+ <img alt="PyPI" src="https://img.shields.io/pypi/v/entropy-data" /></a>
41
+ <a href="https://pypi.org/project/entropy-data/">
42
+ <img alt="Python" src="https://img.shields.io/pypi/pyversions/entropy-data" /></a>
43
+ </p>
44
+
45
+ The `entropy-data` CLI lets you manage your [Entropy Data](https://entropy-data.com) platform from the command line.
46
+
47
+ You can manage data products, data contracts, access agreements, teams, source systems, definitions, certifications, and more — directly from your terminal or CI/CD pipeline.
48
+
49
+ - Docs: [https://docs.entropy-data.com](https://docs.entropy-data.com)
50
+ - PyPI: [https://pypi.org/project/entropy-data/](https://pypi.org/project/entropy-data/)
51
+ - GitHub: [https://github.com/entropy-data/entropy-data-cli](https://github.com/entropy-data/entropy-data-cli)
52
+
53
+ ## Install
54
+
55
+ Requires Python >= 3.11.
56
+
57
+ ```bash
58
+ uv tool install entropy-data
59
+ entropy-data --help
60
+ ```
61
+
62
+ Or with pip:
63
+
64
+ ```bash
65
+ pip install entropy-data
66
+ entropy-data --help
67
+ ```
68
+
69
+ ### Docker
70
+
71
+ ```bash
72
+ docker run --rm entropydata/entropy-data-cli --help
73
+ ```
74
+
75
+ ## Getting Started
76
+
77
+ ### 1. Configure a connection
78
+
79
+ Generate an API key in the [Entropy Data UI](https://app.entropy-data.com) under organization settings, then:
80
+
81
+ ```bash
82
+ entropy-data connection add prod
83
+ # prompts for API key and host
84
+ ```
85
+
86
+ ### 2. Explore your data platform
87
+
88
+ ```bash
89
+ # List teams
90
+ entropy-data teams list
91
+
92
+ # Get a specific data product
93
+ entropy-data dataproducts get my-data-product
94
+
95
+ # List data contracts as JSON
96
+ entropy-data datacontracts list --output json
97
+ ```
98
+
99
+ ### 3. Manage resources
100
+
101
+ ```bash
102
+ # Create or update a team from a YAML file
103
+ entropy-data teams put marketing --file team.yaml
104
+
105
+ # Show the team roles configuration, or switch to a custom role catalog
106
+ entropy-data settings team-roles get
107
+ entropy-data settings team-roles put --file team-roles.yaml
108
+
109
+ # Approve an access agreement
110
+ entropy-data access approve 640864de-83d4-4619-afba-ccea8037ed3a
111
+
112
+ # Search across all resources
113
+ entropy-data search query "customer orders"
114
+ ```
115
+
116
+ ## Commands
117
+
118
+ ```
119
+ entropy-data [--version] [--connection NAME] [--output table|json|yaml] [--debug]
120
+
121
+ connection list | get | add | remove | set-default | test
122
+ dataproducts list | get | put | delete | import-from-git | star | unstar | star-status | stargazers | gitconnection ...
123
+ datacontracts list | get | put | test | delete | yaml | generate | import-from-git | gitconnection ...
124
+ access list | get | put | delete | approve | reject | cancel | request
125
+ teams list | get | put | delete | git-credentials ... | notifications ...
126
+ sourcesystems list | get | put | delete
127
+ definitions list | get | put | delete
128
+ certifications list | get | put | delete
129
+ classifications list | get | put | delete
130
+ policies list | get | put | delete
131
+ example-data list | get | put | delete
132
+ test-results list | get | publish | delete
133
+ costs list | add | delete
134
+ assets list | get | put | delete | tags ...
135
+ tags list | get | put | delete
136
+ api-keys create | delete
137
+ connectors list | get | put | delete
138
+ integrations list | get | runs | runs-get | runs-latest | run | cancel
139
+ organization get | members ... | git-credentials ...
140
+ settings get-customization | put-customization | get-scim-mapping | put-scim-mapping | team-roles ...
141
+ events poll
142
+ lineage list | submit | delete
143
+ schemas get
144
+ search query
145
+ semantics namespaces ... | concepts ... | relationships ... | search
146
+ usage list | submit | delete
147
+ export dir
148
+ apply dir [--include] [--exclude] [--prune] [--dry-run]
149
+ import zip
150
+ sync --source SRC --target TGT --include a,b [--exclude] [--prune] [--dry-run] [--keep DIR]
151
+ ```
152
+
153
+ ## Syncing organization state between instances
154
+
155
+ `sync` copies the portable declarative state of an organization from one Entropy Data
156
+ instance to another — for example to promote a test environment to prod. It exports the
157
+ source and applies it to the target in one step (`export dir` + `apply dir` do the same in
158
+ two). Only state reachable through the public `/api/**` API and portable across instances
159
+ is copied (no secrets, telemetry, or environment-specific identity). Every write is an
160
+ idempotent PUT-by-id, so runs converge and are safe to repeat.
161
+
162
+ `sync` copies **nothing by default** — name the resources to sync with `--include`.
163
+
164
+ **Supported resources** (in dependency order): `teams`, `tags`, `definitions`, `policies`,
165
+ `sourcesystems`, `certifications`, `classification-schemes`, `assets`, `datacontracts`,
166
+ `dataproducts`, `example-data`, `access`, `semantic-namespaces`, `semantic-ontology`,
167
+ `organization-features`.
168
+
169
+ **Not synced:** users & team members, API keys, git credentials, integration and connector
170
+ credentials, usage, costs, test results, events, and lineage (per-instance identity,
171
+ secrets, or telemetry). Organization customization, SCIM mapping, team-roles configuration,
172
+ notification channels, connectors, and integrations are **not supported yet**.
173
+
174
+ ```bash
175
+ # Preview a test -> prod sync of selected resources without writing anything.
176
+ entropy-data sync --source test --target prod --include teams,policies,datacontracts,dataproducts --dry-run
177
+
178
+ # Sync those resources.
179
+ entropy-data sync --source test --target prod --include teams,policies,datacontracts,dataproducts
180
+
181
+ # Mirror: also delete target resources that are absent from the source.
182
+ entropy-data sync --source test --target prod --include datacontracts --prune
183
+
184
+ # The two-step equivalent, with a reviewable YAML tree in between.
185
+ entropy-data -c test export dir ./state
186
+ entropy-data -c prod apply dir ./state
187
+ ```
188
+
189
+ ### `apply dir` — apply a local export tree
190
+
191
+ `apply dir <path>` reconciles a local export directory into the connected instance, in the
192
+ spirit of `kubectl apply -f <dir>`. The tree follows a **folder-as-kind** convention: the
193
+ directory name is the resource kind and each YAML file below it is one resource, addressed
194
+ by the id in its body.
195
+
196
+ ```
197
+ state/
198
+ teams/ # folder name = resource kind
199
+ marketing.yaml # one file per resource (filename is cosmetic)
200
+ policies/
201
+ pii-policy.yaml
202
+ datacontracts/
203
+ orders-1-orders.yaml
204
+ semantic-ontology/
205
+ main.yaml # document resources: one YAML doc per namespace
206
+ organization-features/
207
+ organization-features.yaml # singleton: <name>/<name>.yaml
208
+ ```
209
+
210
+ Unlike `kubectl`, the files carry no `kind:` field — the enclosing folder is authoritative,
211
+ so a file only means what its folder says. Folders that are not a known resource kind are
212
+ ignored. Unlike `sync`, `apply dir` applies the **whole tree by default** (the directory is
213
+ your selection); use `--include`/`--exclude` to narrow it, `--dry-run` to preview, and
214
+ `--prune` to also delete instance resources absent from the tree. This layout matches the
215
+ app's own organization export, so an `export dir` tree and an in-app export zip interchange.
216
+
217
+ Useful options:
218
+
219
+ - `--include a,b` — narrow the apply to these resources (names from the supported list
220
+ above). Optional; the whole tree is applied when omitted.
221
+ - `--exclude a,b` — drop resources from the applied set.
222
+ - `--prune` — after upserts, delete target resources absent from the directory, in reverse
223
+ dependency order. Guarded by a confirmation prompt unless `--yes` is passed.
224
+ - `--dry-run` — print per-resource create/update/(prune) counts; no writes.
225
+
226
+ Notes:
227
+
228
+ - Team members are stripped on import (users are per-instance identities); the export
229
+ keeps them so the artifact is a faithful snapshot.
230
+ - The semantics graph is copied as one OSI ontology YAML document per namespace
231
+ (`semantic-ontology/<namespace>.yaml`) via the app's `.../{ns}/ontology.yaml` endpoint,
232
+ which imports it in the correct internal dependency order and provisions the namespace
233
+ from the metadata (display name, read-only flag, owning team) carried in the document's root
234
+ `custom_properties` — so there is no separate namespace artifact. Requires that endpoint
235
+ on the target instance. A tree exported by an older version that still carries a
236
+ `semantic-namespaces/` folder is applied as before.
237
+ - The organization feature configuration is an org-level singleton
238
+ (`organization-features/organization-features.yaml`), applied last and never pruned. It
239
+ requires the app's `GET`/`PUT /api/organization/features` endpoint (entropy-data#1521),
240
+ which must be merged and deployed to the target instance first.
241
+
242
+ ## Connection Management
243
+
244
+ Connections are stored in `~/.entropy-data/config.toml`:
245
+
246
+ ```toml
247
+ default_connection_name = "prod"
248
+
249
+ [connections.prod]
250
+ api_key = "ed_abc123..."
251
+ host = "https://api.entropy-data.com"
252
+
253
+ [connections.dev]
254
+ api_key = "ed_xyz789..."
255
+ host = "https://localhost:8080"
256
+ ```
257
+
258
+ You can also use environment variables (`ENTROPY_DATA_API_KEY`, `ENTROPY_DATA_HOST`) or CLI options (`--api-key`, `--host`).
259
+
260
+ ### `.env` File Support
261
+
262
+ The CLI automatically loads a `.env` file from the current working directory. This is useful for project-specific configuration:
263
+
264
+ ```bash
265
+ # .env
266
+ ENTROPY_DATA_API_KEY=ed_abc123...
267
+ ENTROPY_DATA_HOST=https://api.entropy-data.com
268
+ ```
269
+
270
+ Values from `.env` are loaded as environment variables and do **not** override already-set environment variables.
271
+
272
+ Resolution precedence: CLI options > environment variables / `.env` > config file.
273
+
274
+ ### TLS behind a corporate proxy or internal CA
275
+
276
+ By default the CLI verifies TLS certificates against the bundled CA certificates (`certifi`). In a corporate network with a TLS-inspecting proxy or an internal certificate authority, this can fail with `CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate`, because the root CA is installed in the operating system's trust store but not in the bundled list.
277
+
278
+ Use the global `--system-truststore` option to verify against the operating system's trust store (macOS Keychain, Windows certificate store, or the system CA certificates on Linux) instead:
279
+
280
+ ```bash
281
+ entropy-data --system-truststore datacontracts list
282
+ ```
283
+
284
+ You can also enable it for every invocation by exporting an environment variable:
285
+
286
+ ```bash
287
+ export ENTROPY_DATA_SYSTEM_TRUSTSTORE=1
288
+ ```
289
+
290
+ This keeps certificate verification on while trusting the corporate root CA, and applies to every command that makes HTTPS requests.
291
+
292
+ ## Development
293
+
294
+ ```bash
295
+ git clone https://github.com/entropy-data/entropy-data-cli
296
+ cd entropy-data-cli
297
+ uv sync --dev
298
+ uv run pytest
299
+ uv run ruff check .
300
+ ```
301
+
302
+ ## Release
303
+
304
+ 1. Update the version in `pyproject.toml`
305
+ 2. Update `CHANGELOG.md` with a `## [X.Y.Z]` section
306
+ 3. Commit, tag, and push:
307
+
308
+ ```bash
309
+ git add pyproject.toml CHANGELOG.md
310
+ git commit -m "Bump version to X.Y.Z"
311
+ git tag vX.Y.Z
312
+ git push origin main --tags
313
+ ```
314
+
315
+ The release workflow will automatically run tests, publish to PyPI, create a GitHub Release, and push a Docker image to Docker Hub.