Can i remove case sensitivity in my bicep file?

[daradona10]

I have created a bicep file that allows the developers in my company to use it to deploy their code via pipeline but for example

as above is the region for 'europe' and 'us'. as you can see i have added the toLower string etc

when i type in EUROPE the pipeline run will fail so when I type in 'europe' it runs perfectly

my question is this. Can i modify my code in any way so that if the developer types in 'EUROPE', 'europe' or 'Europe' that it will allow the pipeline to run successfully?

[brwilkinson]

yaml pipelines also support the same features for allowed + default values.

- name: Task
  displayName: Helm Task
  type: string
  default: upgrade
  values:
  - install
  - upgrade

[brwilkinson]

At the beginning of those yaml files you have screenshots you can parameterize the location value.

i only showed the syntax for a parameter using an example that i had, however you would create one for location.

- name: Location
  displayName: Deployment location
  type: string
  default: northeurope
  values:
  - centralus
  - northeurope

then use the value of the parameter in your task.

--location ${{ parameters.Location }}

[brwilkinson]

@daradona10 did you figure out how to use the specified values in your pipline?

essentially via this method you move parameter binding to the yaml ADO pipeline and it will always pass a lower case to the bicep params.

[brwilkinson]

@daradona10 please keep us posted, if you have a working solution ? I suggest moving the parameter binding, upstream from Bicep to the ADO pipeline itself.

[brwilkinson]

@daradona10 did you try out the yaml parameter option that I listed above, that will ensure the case is always correct?

[brwilkinson]

@daradona10 going to mark this as answered.

Based on:

1. no plans to remove case sensitivity from bicep language.
2. you can do the parameter binding (allowed values) in your yaml pipeline, to ensure bicep received the correct setting/case.

[alex-frankel]

The order of code does not dictate the sequence of events that will be executed. Outputs are processed last, so that's why I think you are perceiving it is not doing anything. If the deployment ran, you would see a deployment output, all lowercase as expected.

Instead, you can use a var and the expression will be calculated prior to the resource being deployed.

Can you share the full code you are running when the error occurs? My guess is you need something like this:

param region string

var lowercasedRegion = toLower(region)

resource foo 'microsoft.foo/bar@2022-04-01' = {
  ...
  location: lowercasedRegion
}

[daradona10]

i tried that. Say for example I type in Europe. It will fail unless I typed in europe. Can it not automatically change it rather than failing the pipeline run and having to retype and run again?