docs: add updated deploy-process

[arealmaas]

Description

Related Issue(s)

• #N/A

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)

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the deployment documentation and CI/CD workflows to incorporate a new environment named YT01. The README has been modified to include YT01 in the deployment process instructions, and the input options in the associated workflow configuration files have been updated to allow selection of the yt01 environment alongside the existing test, staging, and prod options.

Changes

File(s)	Change Summary
README.md	Updated the deployment instructions by renaming "Deploy to Staging (Bump Version and Create Tag)" to "Deploy to Staging and YT01 (Bump Version and Create Tag)".
dispatch-apps.yml, dispatch-infrastructure.yml	Modified input options in the workflows to add yt01 as a valid deployment environment along with test, staging, and prod.

Possibly related PRs

• chore(performance): Add correct permissions to ci-cd-yt01 #1873: Addresses CI/CD workflow changes for the YT01 environment, aligning closely with the modifications in this PR.
• ci: ensure image is published once #1746: Involves revisions to CI/CD workflows that impact deployment configurations for YT01.
• ci: ensure that workflow run name of staging and yt01 contains the version number #1754: Modifies CI/CD workflows to include versioning changes for the YT01 environment, correlating with the updates made here.

Suggested reviewers

• oskogstad

---

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 generate docstrings to generate docstrings for this 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

339-346: Clarify Environment Terminology
The updated deployment step now includes YT01 alongside staging. To improve clarity, consider adding a brief note explaining that YT01 represents the performance environment (or its specific role) so that readers can clearly distinguish between the environments.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~344-~344: Possible missing comma found.
Context: ...ment is tagged with the new <version> without <git-sha> - The new version is buil...

(AI_HYDRA_LEO_MISSING_COMMA)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7b97cea and d579471.

⛔ Files ignored due to path filters (1)

• docs/deploy-process.png is excluded by !**/*.png

📒 Files selected for processing (1)

• README.md (3 hunks)

🔇 Additional comments (2)

README.md (2)

374-374: Updated Workflow Input Options for Applications
The input options for the dispatch-apps.yml workflow now correctly include yt01 along with test, staging, and prod. This update aligns with the PR objectives and improves consistency across environments.

---

388-388: Updated Workflow Input Options for Infrastructure
The environment selection for the dispatch-infrastructure.yml workflow now reflects the addition of yt01, ensuring consistent deployment options.