chore(applications): improve overview of container app revisions

[arealmaas]

Description

Adds a suffix to the revision to it is visible in the overview of revisions what version this is. The existing revision list is very hard to read

Related Issue(s)

• #{issue number}

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)

Documentation

• Documentation is updated (either in docs-directory, Altinnpedia or a separate linked PR in altinn-studio-docs., if applicable)

Summary by CodeRabbit

• New Features

  • Introduced a revisionSuffix parameter for enhanced versioning of container app deployments, allowing for more granular control over which version of a container image is deployed.
  • Improved flexibility and traceability of container application deployments through the ability to specify image tags.

• Bug Fixes

  • Enhanced management of container versions, facilitating easier updates and rollbacks.

[coderabbitai]

Walkthrough

Walkthrough

The pull request introduces a new parameter, revisionSuffix, to the containerApp module across multiple Bicep files. This parameter is assigned the value of imageTag, allowing for enhanced versioning and tagging of container images during deployment. The revisionSuffix parameter is optional and is integrated into the resource definitions, enabling more granular control over the deployment of specific container image revisions.

Changes

Files	Change Summary
.azure/applications/graphql/main.bicep, .azure/applications/web-api-eu/main.bicep, .azure/applications/web-api-so/main.bicep	Added revisionSuffix parameter in containerApp module, assigned the value of imageTag.
.azure/modules/containerApp/main.bicep	Added optional param revisionSuffix string? and modified resource definition to include revisionSuffix.

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 85226cc and 2b8d716.

Files selected for processing (4)

• .azure/applications/graphql/main.bicep (1 hunks)
• .azure/applications/web-api-eu/main.bicep (1 hunks)
• .azure/applications/web-api-so/main.bicep (1 hunks)
• .azure/modules/containerApp/main.bicep (2 hunks)

Additional comments not posted (6)

.azure/modules/containerApp/main.bicep (2)

28-29: LGTM!

The new optional parameter revisionSuffix is declared correctly with a clear description. It enhances the flexibility of the template by allowing users to specify a suffix for the revision of the container app while maintaining backward compatibility.

---

81-81: Looks good!

The revisionSuffix parameter is correctly integrated into the template section of the containerApp resource definition. This ensures that the suffix will be applied to the container app revision during deployment, enabling more granular control over the versioning of the container app.

.azure/applications/graphql/main.bicep (1)

90-90: LGTM! The addition of the revisionSuffix parameter enhances the versioning capabilities of container app deployments.

The introduction of the revisionSuffix parameter to the containerApp module, with its value set to imageTag, enables more granular control over the deployment of specific container image revisions. This change improves the management of container versions and facilitates rollback or updates to specific revisions of the application.

The benefits of this enhancement include:

• Ability to deploy specific versions or tags of the container image
• Improved control over the deployed application revision
• Easier rollback or updates to specific revisions

Great work on implementing this functionality!

.azure/applications/web-api-eu/main.bicep (2)

93-93: LGTM!

The addition of the revisionSuffix parameter to the containerApp module, with its value set to imageTag, is a great improvement. It allows for more granular control over deployments by differentiating between various image revisions based on the specified tag. This change enhances the flexibility and traceability of the container application deployments, aligning with the PR objectives of improving the readability of the revision list for container applications.

---

Line range hint 1-116: Overall approval for the file.

The code changes in this file are focused on adding the revisionSuffix parameter to the containerApp module, with its value set to imageTag. This change enhances the flexibility and traceability of the container application deployments by allowing for more granular control over deployments based on the specified image tag. The implementation is clean and aligns well with the PR objectives of improving the readability of the revision list for container applications. Great work!

.azure/applications/web-api-so/main.bicep (1)

97-97: LGTM! The addition of revisionSuffix parameter enhances the versioning and tagging of container images.

The new revisionSuffix parameter in the containerApp module, with its value set to imageTag, aligns perfectly with the PR objective of improving the readability of the revision list for container applications.

This change provides several benefits:

• It allows for more granular control over the deployment of specific container image revisions.
• It enhances the flexibility in managing different revisions of the container application.
• It is an optional parameter, which means it is unlikely to introduce any breaking changes or errors.

Great work on implementing this improvement!

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud