Using revisions with bicep deployments

[TimoWilhelm]

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Mention any other details that might be useful

One really nice feature of container apps is using multiple revisions and Blue Green Deployments.

I tried to structure a deployment workflow around bicep templates like in this sample repo, but I was unable to get revisions to work correctly. Is this just something that will only be supported by using iterative deployments or will this be possible using the bicep deployment workflow as well?

Documentation or an example for this would be greatly appreciated!

Thanks in advance.

[kendallroden]

Hi @TimoWilhelm when you say you couldn't get revisions to work correctly, what issue did you face?

[TimoWilhelm]

Hi, I was wondering the following:

• How can I create new revisions when using bicep to deploy the resources declaratively?
• Can I keep older revisions when updating the container images when deploying with bicep templates?
• Is there a way to apply traffic splitting in the bicep templates?

Thanks