github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-21 01:11:38 -05:00
Code Issues 856 Packages Projects Releases 74 Wiki Activity

[GH-ISSUE #2174] docker label for blueprints is not accepting an array for sso-roles #2086

New Issue
Closed
opened 2026-04-16 09:04:28 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-16 09:04:28 -05:00
Owner
Copy Link

Originally created by @trexwe on GitHub (Dec 28, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2174

Originally assigned to: @oschwartz10612 on GitHub.

Describe the Bug

I'm adding docker labels to my containers, and I want to add the auth.sso-roles label.

I've tried:

[...].auth.sso-roles=Member
[...].auth.sso-roles=[Member]
[...].auth.sso-roles[0]=Member
[...].auth.sso-roles=["Member"]

The error I'm getting in the newt log:

Blueprint application failed: Failed to apply blueprint from config: Error: Validation error: Invalid input: expected array, received string at "public-resources.[service].auth.sso-roles";

I must not have the right syntax for an array, but I can't figure it out. Please help, or please fix the documentation or code so that it accepts the [0] array like other labels that take arrays with the [0]= syntax.

Environment

  • OS Type & Version: (e.g., Ubuntu 22.04)
  • Pangolin Version: 1.14.1
  • Gerbil Version: 1.3.0
  • Traefik Version: 3.6.5
  • Newt Version: 1.8.1

To Reproduce

add docker labels to a resource, with sso-roles as one of them.

Expected Behavior

Ingest the sso-roles label correctly

Originally created by @trexwe on GitHub (Dec 28, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2174 Originally assigned to: @oschwartz10612 on GitHub. ### Describe the Bug I'm adding docker labels to my containers, and I want to add the auth.sso-roles label. I've tried: [...].auth.sso-roles=Member [...].auth.sso-roles=[Member] [...].auth.sso-roles[0]=Member [...].auth.sso-roles=["Member"] The error I'm getting in the newt log: ``` Blueprint application failed: Failed to apply blueprint from config: Error: Validation error: Invalid input: expected array, received string at "public-resources.[service].auth.sso-roles"; ``` I must not have the right syntax for an array, but I can't figure it out. Please help, or please fix the documentation or code so that it accepts the [0] array like other labels that take arrays with the [0]= syntax. ### Environment - OS Type & Version: (e.g., Ubuntu 22.04) - Pangolin Version: 1.14.1 - Gerbil Version: 1.3.0 - Traefik Version: 3.6.5 - Newt Version: 1.8.1 ### To Reproduce add docker labels to a resource, with sso-roles as one of them. ### Expected Behavior Ingest the sso-roles label correctly
GiteaMirror commented 2026-04-16 09:04:29 -05:00
Author
Owner
Copy Link

@Noggog commented on GitHub (Jan 3, 2026):

Hmm, after some playing around, this did work for me:

    labels:
      - pangolin.proxy-resources.docs.auth.sso-roles[0]=Member
      - pangolin.proxy-resources.docs.auth.sso-roles[1]=Newbie
<!-- gh-comment-id:3706596781 --> @Noggog commented on GitHub (Jan 3, 2026): Hmm, after some playing around, this did work for me: ``` labels: - pangolin.proxy-resources.docs.auth.sso-roles[0]=Member - pangolin.proxy-resources.docs.auth.sso-roles[1]=Newbie ```
GiteaMirror commented 2026-04-16 09:04:30 -05:00
Author
Owner
Copy Link

@LunkSnee commented on GitHub (Jan 12, 2026):

Hmm, after some playing around, this did work for me:

    labels:
      - pangolin.proxy-resources.docs.auth.sso-roles[0]=Member
      - pangolin.proxy-resources.docs.auth.sso-roles[1]=Newbie

Thanks, Noggog. Did it work for you if you just had 1, only Member, not Newbie

<!-- gh-comment-id:3736592009 --> @LunkSnee commented on GitHub (Jan 12, 2026): > Hmm, after some playing around, this did work for me: > > ``` > labels: > - pangolin.proxy-resources.docs.auth.sso-roles[0]=Member > - pangolin.proxy-resources.docs.auth.sso-roles[1]=Newbie > ``` Thanks, Noggog. Did it work for you if you just had 1, only Member, not Newbie
GiteaMirror commented 2026-04-16 09:04:30 -05:00
Author
Owner
Copy Link

@Noggog commented on GitHub (Jan 12, 2026):

Yes, it has been working for me with just a single entry so far

<!-- gh-comment-id:3736755218 --> @Noggog commented on GitHub (Jan 12, 2026): Yes, it has been working for me with just a single entry so far
GiteaMirror commented 2026-04-16 09:04:31 -05:00
Author
Owner
Copy Link

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

Sounds like this is "resolved"? If I am wrong please feel free to reopen!

<!-- gh-comment-id:3771146228 --> @oschwartz10612 commented on GitHub (Jan 20, 2026): Sounds like this is "resolved"? If I am wrong please feel free to reopen!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#2086
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?