Azure / Azure/bicep

Release `generator` and `autorest.bicep` as public npm packages

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

Description

**Is your feature request related to a problem? Please describe.**
To generate Bicep Extensibility Provider Types, I am required to keep a copy of the `generator` and `autorest.bicep` code see here for example:
* https://github.com/Azure/bicep-types-k8s/tree/main/src/generator
* https://github.com/Azure/bicep-types-az/tree/main/src/generator
* https://github.com/Azure/bicep-types-k8s/tree/main/src/autorest.bicep
* https://github.com/Azure/bicep-types-az/tree/main/src/autorest.bicep

This presents several problems:

* If the type definition format changes, I am required to update and reconcile conflicts on the generator code
* Keeping the different copies synchronized is unwieldy

**Describe the solution you'd like**

Publish `generator` and `autorest.bicep` as versioned npm packages thus removing the need for keeping copies of the code

Contributor guide

Open the contributing guide

Research direction

Review the generator and autorest.bicep copies linked under bicep-types-k8s and bicep-types-az to understand their package boundaries and synchronization needs. Define versioned public npm packages for both components so downstream projects no longer need to keep local copies; completion means consumers can depend on the published packages.

Written by the indexing model from the issue text.

Assessment

Domain
release, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.