[^1]: Approve pending prod releases by clicking the blue production chip and clicking approve.
[^2]: Look for any blue production chips.
[^3]: This is done after checking that everything is running as it should.
[^4]:
Check if there are any awaiting deployments to production for Auditlog
Click on the awaiting deployment. You can see that a deployment to TT02 was successfull last week. Click on Review deployments
Click on the prod checkbox and then click approve and deploy. This will trigger a deployment to production.
[^5]:
The new components are deployed via github actions. For auditlog, a release is scheduled every wednesday. Go to Auditlog Releases and check if there are any draft release is found.
click on Edit Draft and set the release title as the tag version f.eks in the picture you can see that the tag is 2024.4.3 and the release title therefore should be set as 2024.4.3.
Scroll down and you will find the button "Publish Release"
once the publish release is clicked, release notes will be published and a deploy will be triggered to TT02.
You can see that the deploy is triggered and the approvers are notified about the awaiting deployment of Auditlog
Click on the awaiting deployment
Click on review deployments. Click the tt02 checkbox and click approve and deploy button
Now you can see that a deployment is triggered to TT02
Once the package is successfully deployed to TT02, you can see that a deployment to production is triggered. This will be approved by the deployer on the following Tuesday
[^6]:
Verify that the newly deployed package has the right image tag
Check the provisioning status in the container apps overview page
[^7]:
Verify the function app deployment status in the deployment logs in deployment center of the function app
Tuesday
#resourceregistryand#authentication. If none of them have been deployed the last week, no change needed.Wednesday
#resourceregistryand#authentication. If none of them have been deployed the last week, no change needed.Thursday
Go through all github pull-requests from the dependency bots in all repos.
[^1]: Approve pending prod releases by clicking the blue production chip and clicking approve.
[^2]: Look for any blue production chips. 
[^3]: This is done after checking that everything is running as it should.
[^4]:
Check if there are any awaiting deployments to production for Auditlog
Click on the awaiting deployment. You can see that a deployment to TT02 was successfull last week. Click on Review deployments
Click on the prod checkbox and then click approve and deploy. This will trigger a deployment to production.
[^5]: The new components are deployed via github actions. For auditlog, a release is scheduled every wednesday. Go to Auditlog Releases and check if there are any draft release is found.
click on Edit Draft and set the release title as the tag version f.eks in the picture you can see that the tag is 2024.4.3 and the release title therefore should be set as 2024.4.3.
Scroll down and you will find the button "Publish Release"
once the publish release is clicked, release notes will be published and a deploy will be triggered to TT02.
You can see that the deploy is triggered and the approvers are notified about the awaiting deployment of Auditlog
Click on the awaiting deployment
Click on review deployments. Click the tt02 checkbox and click approve and deploy button
Now you can see that a deployment is triggered to TT02
Once the package is successfully deployed to TT02, you can see that a deployment to production is triggered. This will be approved by the deployer on the following Tuesday
[^6]: Verify that the newly deployed package has the right image tag
Check the provisioning status in the container apps overview page
[^7]: Verify the function app deployment status in the deployment logs in deployment center of the function app
