sefe / sefe/dorc

Implement Containers, Cloud, and APIs environment component tabs

Open
#780 0 comments 0 reactions 1 assignee View on GitHub

@kirill-suspitsin-ext-sefe is already working on this.

Since Jul 27, 2026.

  • #773 by @hegsie — open
Dominant language
C#
Stars
5
Forks
3
Avg merge
1d 22h
Merged PRs (30d)
14

Description

Problem

The Containers, Cloud, and APIs sub-tabs under environment details are placeholders. Users cannot manage these component types, associate them with environments, audit changes, or expose them as deployment variables.

Scope

  • Add persistent models for containers, cloud resources, and API registrations, including environment mappings and audit records.
  • Provide CRUD and environment attach/detach operations with explicit outcomes and conflict handling.
  • Add typed API endpoints with environment-aware authorization and appropriate 403, 404, and 409 responses.
  • Register the new persistence and resolver dependencies in the API and Monitor.
  • Emit environment-level and per-tag deployment variables for attached components without changing variables for unaffected environments.
  • Replace the placeholder UI tabs with grids and create, edit, attach, detach, and delete workflows.
  • Gate write controls using the environment's edit permission.

Acceptance criteria

  • Users can create, view, edit, attach, detach, and delete all three component types through the environment details UI.
  • Every write operation is authorized and audited, including attach and detach actions.
  • Concurrent or duplicate environment mappings return conflicts rather than false success responses.
  • Attached components produce the documented deployment variables, including scalar or array per-tag name values as appropriate.
  • Environments without attached components retain their existing deployment variable set unchanged.
  • Deep links and cold-cache tab activation load the correct component data.
  • Automated tests cover persistence, authorization, API outcomes, dependency registration, variable resolution, and UI behavior.

Rollout notes

  • Deploy the database dacpac before the API and Monitor.
  • Check existing properties for collisions with the new reserved deployment variable names and prefixes.
  • Complete a deployed UI round-trip covering create, attach, edit, detach, and delete.

Implementation

Implemented by #773.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.