Blueprint-managed resources: visual indicator, edit warning, and unlock option

[strausmann]

Problem

When resources are created via Docker label blueprints, there is no way to tell them apart from manually created resources — not in the dashboard, and not via the API.

This causes a frustrating workflow: you make a change to a resource in the UI (e.g., adjust SSO roles or access rules), and seconds later it gets silently overwritten by the next blueprint sync. You then have to go investigate whether this resource was created by a blueprint or manually — check the Docker labels on the compose stack, check the Newt logs, try to remember.

The same problem exists via the API: when querying a resource (GET /resource/{id}), there is no field indicating whether it is blueprint-managed. An API consumer has no way to know that modifying this resource is pointless because the next sync will revert the change. Instead, the change needs to be made in the Docker compose labels on the stack.

Proposed Solution

1. Visual Indicator in Resource List and Detail View

Add a visible marker to blueprint-managed resources:

• A badge, icon, or tag in the resources overview (e.g., a small sync icon or "Blueprint" label)
• Visible at a glance without clicking into each resource
• Allows administrators to immediately know: "this one I need to change in the compose stack, not here"

2. Edit Warning on Blueprint-Managed Resources

When opening the settings of a blueprint-managed resource, show a warning:

⚠️ This resource is managed by a Docker label blueprint. Manual changes will be overwritten on the next sync (container restart, Newt reconnect, or dashboard visit). To make permanent changes, update the Docker labels in your compose stack.

Optionally: make fields read-only by default with an explicit "Override" toggle for cases where you know what you are doing.

3. API: Return Blueprint Source in Resource Response

Add a field to the resource API response indicating blueprint management:

{
  "resourceId": 66,
  "name": "GitLab",
  "fullDomain": "git.example.com",
  "blueprintManaged": true,
  "blueprintSource": {
    "siteId": 3,
    "siteName": "HHDOCKER01",
    "containerName": "gitlab",
    "lastApplied": "2026-04-13T15:30:00Z"
  }
}

This allows API consumers and automation tools to:

• Skip modifications on blueprint-managed resources
• Direct the user to the correct compose stack for changes
• Build dashboards showing which resources are automated vs. manual

4. Detach / Unlock from Blueprint

Provide an option to permanently detach a resource from its blueprint:

• "Detach from Blueprint" action in the UI or via API
• After detaching, blueprint sync no longer overwrites this resource
• Useful when the initial setup was done via blueprint but ongoing management should be manual
• Also needed when Docker labels have been removed but the resource should persist without being re-linked if labels are added back

Related Issues / Discussions

• Blueprint overwriting non configured settings #2197 — Blueprint overwriting non-configured settings
• Error - Can not save general settings in blueprinted resource #1737 — Error saving settings in blueprinted resource
• How remove blueprint using Pangolin gui? #1815 — How to remove blueprint using Pangolin GUI
• Are docker compose blueprints suppose to apply constantly? #1925 — Blueprints applying constantly on container events

[Loapu]

Wouldn't it be "enough" if you could just... attach labels to resources in blueprints? As of now, you can only attach labels manually, not via blueprints.

[oschwartz10612]

We should fix this! Will try to do so for this next release!

[oschwartz10612]

Labels on the blueprints will be available in 1.22. 03118f1