Azure/bicep

Support "importing" resourceType and apiVersion mappings for specific resource types

alex-frankel opened this issue · 5 comments

alex-frankel commented

can we allow for import of resourceType and/or apiVersion combinations for end users to declare resources without worrying as much about those details? essentially modules for types & apiVersions

bterlson commented

Resource types and versions feel a bit different to me. Resource types can be implicit. Versions need to be explicit somewhere, somehow. The biggest problem with versioning in the current ARM language is how they need to be sprinkled everywhere. You could imagine having a top-level apiVersion declaration for each RP so it's super clear and explicit what api versions are being used but isn't super verbose?

FWIW for the JS prototype I was considering opting into versions based on the particular package version for the RP you installed (e.g. @azure/arm-storage@1.0.0 maps to api version 2019-12-01).

alex-frankel commented

can you talk a little bit more about how resource types can be implicit? What would be an example of that?

alex-frankel commented

Need more clarity on how important this is and how much modules could potentially help with this problem

slavizh commented

Made suggestion in #413 that might be related to this.

alex-frankel commented

Closing and tracking with #622