radius-project / radius-project/docs
Create/Update docs to capture container --> UDT connection and udt--> udt
Open
Nobody has claimed this yet.
triaged
- Dominant language
- Bicep
- Stars
- 26
- Forks
- 52
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
What content needs to be created or modified?
We can now have a container connect to UDT to get some variables auto-injected as environment variables.
We should have some content capturing sample manifest, bicep and how-to that enables understanding this feature.
Describe the solution you'd like
Where should the new material be placed?
The associated pull request from the Radius code repo, if applicable
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the existing container and UDT documentation and sample manifests, then verify the container-to-UDT and UDT-to-UDT environment-variable flows. Done means the documentation includes a sample manifest, Bicep example, and how-to covering this feature.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100