Azure / Azure/bicep

Describe contextual input values propagated the Extensibility Provider (EP) in the design of #3565

Open
#6,628 0 comments 0 reactions 0 assignees View on GitHub
enhancement story: extensibility
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 2h
Merged PRs (30d)
79

Description

Would it be possible to describe what input values (such as the `Authorization` header) are propagated to the Extensibility Provider (EP) ?

In the case of credentials/secrets (like the k8s kubeconfig) what is the trust model?

_Originally posted by @asilverman in https://github.com/Azure/bicep/issues/3565#issuecomment-1106831611_

Contributor guide

Open the contributing guide

Research direction

Start by reading the design discussion in issue #3565 and its linked context. Document which contextual inputs reach the Extensibility Provider, including authorization headers, and explain the trust model for credentials such as a Kubernetes kubeconfig; done means both propagation and credential-handling questions are answered clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
documentation, security
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.