containerApp evn var collections

[et1975]

The changes in this PR are as follows:

• Adds support for passing a collection of env variables of a given type to containerApp
  Why is this useful? In the absence of broad support for _.For in this library this makes iterators possible and brings it to parity with some other CEs.

I have read the contributing guidelines and have completed the following:

• Tested my code end-to-end against a live Azure subscription.
• Updated the documentation in the docs folder for the affected changes.
• Written unit tests against the modified code that I have made.
• Updated the release notes with a new entry for this PR.
• Checked the coding standards outlined in the contributions guide and ensured my code adheres to them.

If I haven't completed any of the tasks above, I include the reasons why here:

Below is a minimal example configuration that includes the new features, which can be used to deploy to Azure:

                containerApp {
                    name "multienv"
                    add_simple_container "mcr.microsoft.com/dotnet/samples" "aspnetapp"
                    ingress_target_port 80us
                    ingress_transport Auto
                    add_http_scale_rule "http-scaler" { ConcurrentRequests = 10 }
                    add_cpu_scale_rule "cpu-scaler" { Utilisation = 50 }
                    add_secret_parameters ["servicebusconnectionkey"]
                    add_env_variables ["ServiceBusQueueName","wishrequests"]
                    add_secret_expressions ["containerlogs", containerLogs.PrimarySharedKey]
                }

[et1975]

Added a fix for #921

[et1975]

I don't think line 51 is correct actually, wondering if I should fix that too. I'm thinking it should be managedEnvironments.resourceId.

[ninjarobot]

Yes, you are right, it's the managed environment, so this is a lurking bug.

[et1975]

@forki what do you think?

[ninjarobot]

The new operations look good, thank you for adding those and the tests to use them.

Are the ACR changes just a temporary workaround?

[ninjarobot]

Yes, you are right, it's the managed environment, so this is a lurking bug.

[ninjarobot]

I take it we just need this for now until this bug is fixed, right?

[isaacabraham]

I think so, yes. Although the string concatenation approach should just work, once the underlying ARM provider is fixed I would prefer to revert to the original expression-based approach.

[ninjarobot]

Sounds good, and given we do t have to change the DSL, this will just keep working when they fix the bug. LGTM.

[ninjarobot]

Thanks for the contribution, this is released in 1.7.1 and available on nuget.