Repository navigation
Conversation
…data-service Adds shared Artifact Apps contracts (PLAN §6/§8/§9): status/visibility/runtime enums, publish/update/version request schemas, response types, query keys, API endpoint builders, and data-service calls. Registers ARTIFACT_APP in the ResourceType/AccessRoleIds enums and permission-bit mapping. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds ArtifactApp and ArtifactVersion schemas, models, and DB methods (PLAN §6.1/§6.2): atomic app+version creation, tenant-scoped queries, version lifecycle (draft/release/activate/withdraw), SHA-256 source hashing, and an idempotent index migration (§6.4). Includes unit tests against an in-memory MongoDB covering CRUD, tenant isolation, snapshot integrity, and immutability. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…ctions Wires ARTIFACT_APP into the existing ACL system (PLAN §7): seeds Owner/Editor/Viewer access roles, adds READ/MANAGE_ARTIFACT_APPS capabilities with ResourceCapabilityMap bypass, and registers artifact audit actions. Makes the share middleware permission map partial so capability-governed resources need no PermissionTypes entry. Updates role/capability tests. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Add the /api/artifact-apps surface (WP3/WP4): typed publishing, CRUD, and version-lifecycle (create/release/activate/withdraw) handlers in packages/api, backed by the existing ACL system and audit log. Actor identity and tenant are derived strictly from the authenticated session per §8.7. Full-source snapshots are immutable once released. Includes mongodb-memory-server integration tests. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…(WIP WP5/WP6) Partial frontend work: standalone app view, app renderer wrapper, react-query queries/mutations for artifact-apps endpoints, i18n keys. Committed to preserve progress before credit exhaustion.
Documents what is done (WP0-WP4 backend + partial WP5/WP6 frontend) and what remains (build verification, WP5 routing, WP6 publish UI, combined PR) so a resuming agent can pick up without re-discovery.
dsheine
changed the title
|
Heads up @dsheine — I brought this up to date on current Two things the merge surfaced, plus test coverage for the authorization layer, are described on #14616. Nothing there is meant to bypass your PR — it's so CI actually exercises this and so the ACL has evidence behind it before anyone reviews the design. Happy to hand the branch back for you to pull into your fork if you'd rather keep everything on this PR. |
|
No worries, I it's not "my" work anyways (Perplexity and Copilot). Sorry for the inactivity, but I'll hopefully find some time for the PR in the future |
|
@danny-avila can I just check you're not planning to look at this anytime soon? And assume @dsheine you won't either. If so I will get my team to look at this as a priority. Without doubt, this will be an immensely powerful feature and has been requested my lots of users in my org. I would argue, this could be a viewed as a very lightweight 1st step to compete with ChatGPT's new 'Sites'. |
|
@will171125 I won't because I currently don't have the resources right now I am really sorry |
This branch has not been deployed
3 participants
Standalone Artifact Publishing and Sharing
Summary
Artifacts can now be published and shared as "Apps"
Change Type
Please delete any irrelevant options.
Testing
Please describe your test process and include instructions so that we can reproduce your test. If there are any important variables for your testing configuration, list them here.
Test Configuration:
Checklist
Please delete any irrelevant options.
Implements #13374
I tested the feature but translation work has yet to be done. No known bugs (atm)