Initial features needed for Bicep
Open
Nobody has claimed this yet.
Area-Bicep
Issue-Enhancement
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
- not()
- or()
- and()
- automatic consumption of .bicep files
- output
- union()
- contains()
- endsWith()
- length()
- utcNow()
- uniqueString()
- empty()
- Copy (aka loops)
- Types
- map() - lambda
- filter() - lambda
- reduce() - lambda
- ARM language v2 support
- flatten() -ARM language v2
Proposed technical implementation details (optional)
No response
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
Use the unchecked items in the issue as the scope, beginning with output, Types, and the lambda functions. The issue names no files, entry points, or tests, so first locate the existing Bicep feature handling in the DSC repository and its tests. Done is not defined beyond implementing the selected Bicep capabilities and ARM language support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100