[GH-ISSUE #2216] Blueprints do not support wildcards in alias for private resources #2102

New Issue

GiteaMirror · 2026-04-16T09:05:45-05:00

GiteaMirror commented

2026-04-16 09:05:45 -05:00

Originally created by @Bhuemann on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2216

Originally assigned to: @oschwartz10612 on GitHub.

Describe the Bug

Private resources support wildcards as described in documentation; however, they are not supported declaratively within blueprints.

e.g. The following blueprint

private-resources:
  past-texas-coral-snake:
    name: Internal Network
    mode: host
    destination: 192.168.2.117
    site: difficult-groundhog
    alias: "*.int.domain.com"

Results to the following error:

Environment

OS Type & Version: Running via docker on Ubuntu 22.04.1 LTS
Pangolin Version: 1.14.1
Gerbil Version: 1.3.0
Traefik Version: 3.6
Newt Version: 1.8.1
Olm Version: (if applicable)

To Reproduce

Navigate to blueprints, create new blueprint
Give blueprint a name with contents:

private-resources:
  past-texas-coral-snake:
    name: Internal Network
    mode: host
    destination: 192.168.2.117
    site: difficult-groundhog
    alias: "*.int.domain.com"

Select 'apply blueprint'

Expected Behavior

The blueprint is correctly validated and alias is set to *.int.domain.com

Originally created by @Bhuemann on GitHub (Jan 6, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2216 Originally assigned to: @oschwartz10612 on GitHub. ### Describe the Bug Private resources support wildcards as described in [documentation](https://docs.pangolin.net/manage/resources/private/alias); however, they are not supported declaratively within blueprints. e.g. The following blueprint ``` private-resources: past-texas-coral-snake: name: Internal Network mode: host destination: 192.168.2.117 site: difficult-groundhog alias: "*.int.domain.com" ``` Results to the following error: <img width="494" height="148" alt="Image" src="https://github.com/user-attachments/assets/8953ff74-edc7-44f1-b68e-07b8f0d5de8b" /> ### Environment - OS Type & Version: Running via docker on Ubuntu 22.04.1 LTS - Pangolin Version: 1.14.1 - Gerbil Version: 1.3.0 - Traefik Version: 3.6 - Newt Version: 1.8.1 - Olm Version: (if applicable) ### To Reproduce 1. Navigate to blueprints, create new blueprint 2. Give blueprint a name with contents: ``` private-resources: past-texas-coral-snake: name: Internal Network mode: host destination: 192.168.2.117 site: difficult-groundhog alias: "*.int.domain.com" ``` 3. Select 'apply blueprint' ### Expected Behavior The blueprint is correctly validated and alias is set to `*.int.domain.com`

GiteaMirror added the bug label 2026-04-16 09:05:45 -05:00

GiteaMirror closed this issue

2026-04-16 09:05:46 -05:00

GiteaMirror commented

2026-04-16 09:05:48 -05:00

@PavanendraBaahubali commented on GitHub (Jan 6, 2026):

hey, @oschwartz10612 can i work on this?

@PavanendraBaahubali commented on GitHub (Jan 6, 2026): hey, @oschwartz10612 can i work on this?

GiteaMirror commented

2026-04-16 09:05:48 -05:00

@oschwartz10612 commented on GitHub (Jan 6, 2026):

@PavanendraBaahubali sure that would be super cool! If you dont get to it we will shortly for a patch probably.

I think this should be a fairly simple fix in the server/lib/blueprints/proxyResources.ts or server/lib/blueprints/types.ts files.

@oschwartz10612 commented on GitHub (Jan 6, 2026): @PavanendraBaahubali sure that would be super cool! If you dont get to it we will shortly for a patch probably. I think this should be a fairly simple fix in the `server/lib/blueprints/proxyResources.ts` or `server/lib/blueprints/types.ts` files.

GiteaMirror commented

2026-04-16 09:05:49 -05:00

@PavanendraBaahubali commented on GitHub (Jan 6, 2026):

Yeah it's just simple fix. Problem in zod validation regex. I will submit pr now

@PavanendraBaahubali commented on GitHub (Jan 6, 2026): Yeah it's just simple fix. Problem in zod validation regex. I will submit pr now

GiteaMirror commented

2026-04-16 09:05:50 -05:00

@eamonflanaganmurphy commented on GitHub (Feb 16, 2026):

is this complete? I still have the same issue and cannot add wildcards in alias for private resources

@eamonflanaganmurphy commented on GitHub (Feb 16, 2026): is this complete? I still have the same issue and cannot add wildcards in alias for private resources

GiteaMirror commented

2026-04-16 09:05:51 -05:00

@oschwartz10612 commented on GitHub (Feb 25, 2026):

@eamonflanaganmurphy should be. Are you on the latest version? Could you provide the error you receive?

@oschwartz10612 commented on GitHub (Feb 25, 2026): @eamonflanaganmurphy should be. Are you on the latest version? Could you provide the error you receive?