Skip to content

Feature: Add Deployment Profile#17

Merged
JTNing merged 5 commits into
mvpfrom
feature/deployment-profile
Jun 20, 2026
Merged

Feature: Add Deployment Profile#17
JTNing merged 5 commits into
mvpfrom
feature/deployment-profile

Conversation

@JTNing

@JTNing JTNing commented Jun 20, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

JTNing and others added 5 commits June 14, 2026 19:43
Introduce JSON Deployment Profiles and a backend that resolves feature and
guided-option availability from the active profile's provided capabilities.

- bootstrap profiles default-teacher-profile and ai-enabled-profile under
  src/main/resources/deployment-profiles, with secret references only
- deployment package: DeploymentProfile domain, file-backed repository
  (classpath bootstrap + data/deployment-profiles override), service,
  CapabilityResolutionService, DTOs, and controlled DeploymentProfileException
- GET /api/deployment-profiles, GET /api/deployment-profiles/{id}, and
  GET /api/feature-model/profile-availability?profileId= (default + per-profile)
- capabilities are read from guided-workflow option requiresCapabilities; the
  teacher-facing reason hides raw ids while advanced views keep them

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Integrate deployment-profile availability into the guided Configurator.

- header profile selector switches the active deployment profile and reconciles
  the current selection, removing now-unavailable features with a clear note
- guided option cards are disabled with a readable teacher-facing reason when
  the active profile lacks their capabilities; raw capability ids stay out of
  the cards
- review page shows the active profile and a profile-dependent feature summary
- advanced tree debug view shows availability and the exact missing capability
  ids for the selected feature
- workflow warnings no longer leak raw capability ids
- FeatureModelService.loadWorkflowAvailability and deployment-profile types

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Apply the Phase 4 reassessment: teachers configure functional features only and
are never asked to choose a Deployment Profile.

- replace the two bootstrap profiles with a single default-artemis-profile that
  provides every referenced capability and a richer, evidence-backed parameter
  set (Iris/Athena/Spring AI/Atlas/Theia/Sharing + baseline); secrets are env:
  references only
- DeploymentProfileService.DEFAULT_PROFILE_ID -> default-artemis-profile
- remove the header profile selector, onSelectProfile, and profile-switch
  reconciliation; keep capability gating as a latent safety net for maintainer
  local overrides
- neutral review wording ("Deployment context loaded") and a "needs deployment
  setup" list; reframe the option hint to "Requires deployment setup"
- keep GET /api/feature-model/profile-availability?profileId= for tests/debug and
  the advanced tree missing-capability view
- update backend and frontend tests for the single profile

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
# Conflicts:
#	src/main/webapp/app/feature-model/configurator/feature-model-configurator.component.ts
@JTNing JTNing merged commit b4315a3 into mvp Jun 20, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant