Engin Polat

This issue is resolved in the `bicep` repo ; https://github.com/Azure/bicep/issues/13463#issuecomment-1971233829 I can't close this issue, can I get help to close it @yonzhan , since the same issue on the...

This [Design Proposal - Modular Parameters](https://github.com/Azure/bicep/issues/12019) could be the solution for this request. Your example above can be achieved like this; ```bicep // environment variables env="dev" // main.bicep @description('Location for...

hi @mennolaan, we decided to take another look at our design proposal. I'll update the design proposal (and post a comment here) when we have an updated proposal with all...

> Will there be a specific syntax for importing all param values from a file? great question! Importing everything from a separate file could be dangerous, since you have to...

> I like these ideas Perhaps something a little cleaner > > ``` > param location = import(location, ./foo.bicepparam) // This imports a single value > import(./bar.bicepparam) // This imports...

> will this support `shadow param`? > > for exmaple > > default.bicep > > ``` > param a int = 1 > param b int = 2 > ```...

> I would like to see both a wildcard import to import all parameters from a given file in addition to selecting specific params. Wildcard imports could be dangerous and...

> How would name conflicts be handled between files? Personally, I'd prefer a preference towards specificity (e.g. import the specifically named import over a wildcard, but show a squiggly line...

> Expanding on this, seen customers where they like the generate a parameter file for an entire environment which will support multiple deployments. Was wondering if we could then do...

we have a draft PR is up (https://github.com/Azure/bicep/pull/13900) our plan is to make it to the next release, behind a feature flag.