Credential-less provider profiles cannot be instantiated without a credential source
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 68/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- rust
- Ambito
- cli, networking
Direzione di ricerca
Riproduci il comportamento con i comandi provider profile lint, import e create mostrati nell’issue, usando un profilo con credentials: []. Traccia il punto di ingresso della creazione del provider e la relativa convalida dell’origine delle credenziali. Il lavoro è completato quando i profili senza credenziali possono essere creati e associati a un sandbox, mentre i profili con credenziali continuano a richiedere la propria origine configurata e gli endpoint rimangono nella policy di rete effettiva.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
User Story
As an OpenShell user, I want to create a provider instance from a provider profile that declares no credentials, so that I can use the provider solely to distribute network access policies to sandboxes.
This is useful for internal services and public endpoints where authentication is not required, but where the provider profile is still useful for managing and attaching network policy.
Problem Statement
A valid provider profile with credentials: [] can be linted and imported successfully, but a provider instance cannot be created from that profile without supplying one of the credential-source options.
For example, a profile containing only a TCP endpoint and no credentials is accepted by the profile validation/import commands, but:
openshell provider create --name example --type example
fails because the CLI requires a credential source.
This prevents credential-less, policy-only provider profiles from being instantiated.
Impact / Why This Matters
Users who want to use provider profiles purely to distribute network policies must currently provide a credential source even when the provider profile does not require credentials.
As a workaround, users have to provide a dummy/fake secret when creating the provider instance.
This creates unnecessary configuration and makes the provider appear to have credentials when it does not actually require or use any.
For policy-only providers, this also makes it impossible to use the provider model as intended without introducing artificial credentials into the configuration.
Acceptance Criteria
- A provider profile containing
credentials: []can be instantiated without providing a credential source. - The following command succeeds for a credential-less provider profile:
openshell provider create --name example --type example
- No dummy, fake, or otherwise unnecessary credential is required.
- The resulting provider instance can be attached to a sandbox.
- Endpoints defined by the provider profile are included in the sandbox's effective network policy.
- Existing provider profiles that require credentials continue to require their appropriate credential sources.
Reproduction Steps
Create /tmp/example-provider.yaml:
id: example
display_name: Example
description: Credential-less TCP access to example.com
category: other
inference_capable: false
credentials: []
endpoints:
- host: example.com
port: 443
protocol: tcp
binaries:
- /usr/bin/curl
2. Validate the profile
openshell provider profile lint -f /tmp/example-provider.yaml
Expected:
Provider profile lint passed.
3. Import the profile
openshell provider profile import \
-f /tmp/example-provider.yaml
The profile is imported successfully.
4. Try to create a provider without credentials
openshell provider create \
--name example \
--type example
Actual result:
error: the following required arguments were not provided:
<--from-existing|--credential ...|--from-gcloud-adc|--runtime-credentials|--from-oidc-token>
The profile explicitly declares:
credentials: []
but the provider creation command still requires a credential-source option.
5. Workaround
The provider can only be created by supplying a credential source, for example by using a dummy/fake secret.
This is unnecessary because the provider profile itself declares that it has no credentials.
Environment
- OpenShell:
0.0.116 - OS: macOS 26.6.2
- Deployment: OpenShell gateway running locally, docker desktop 4.90.0, docker engine 29.7.2,
- Provider type: custom provider profile
- Provider profile: credential-less (
credentials: []) - Network policy: TCP endpoint
example.com:443
Logs
$ openshell provider create --name example --type example
error: the following required arguments were not provided:
<--from-existing|--credential ...|--from-gcloud-adc|--runtime-credentials|--from-oidc-token>
- Lingua principale
- Rust
- Stelle
- 8.7k
- Fork
- 1.3k
- Merge medio
- 2g 7h
- PR unite (30g)
- 243
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di NVIDIA/OpenShell
-
area:docs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
state:triage-needed
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
area:cli state:validated
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
state:triage-needed
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
-
area:build spike state:review-ready state:stale
Difficoltà 2/5 Mezza giornata Idoneità per principianti 68/100
Tutte le issue di NVIDIA/OpenShell
Issue simili
-
risk:low runtime status:in-progress type:test
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
zeroclaw-labs/zeroclaw#11023 ·
-
good first issue refactor
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
EricSpencer00/Resilient#4835 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
bisq-network/bisq-musig#204 ·
-
agent:ready documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
cesarferreira/stax#890 ·