Deploy & Patching W17

by ADMIN 22 views

=====================================

Tuesday

Deploy All Components to Production

The first step in the deployment process is to deploy all components to production. This involves deploying the following components:

  • Authentication: This component is responsible for handling user authentication and authorization.
  • Resource Registry: This component is responsible for managing resources and their associated metadata.
  • Register: This component is responsible for registering new resources and updating existing ones.
  • Auditlog: This component is responsible for logging and auditing all changes made to the system.

To deploy these components, follow these steps:

  1. Deploy Authentication: Deploy the Authentication component to production by clicking on the blue production chip and approving the pending release.
  2. Deploy Resource Registry: Deploy the Resource Registry component to production by clicking on the blue production chip and approving the pending release.
  3. Deploy Register: Deploy the Register component to production by clicking on the blue production chip and approving the pending release.
  4. Deploy Auditlog: Deploy the Auditlog component to production by clicking on the blue production chip and approving the pending release.

Deploy Updates to APIM

The next step is to deploy updates to APIM (Azure API Management). This involves checking for updates to the following products:

  • #resourceregistry
  • #authentication
  • #register

If none of these products have been updated in the last week, no changes are needed. Otherwise, run the APIM prod pipeline and select the product that needs to be updated.

Post-Deploy All Components in Production

After deploying all components to production, the next step is to post-deploy all components in production. This involves checking the AKS workloads for each component and verifying that they are running as expected.

  1. Post-Deploy Authentication: Post-deploy the Authentication component by checking the AKS workloads and verifying that the daemon set is running as expected.
  2. Post-Deploy Resource Registry: Post-deploy the Resource Registry component by checking the AKS workloads and verifying that the daemon set is running as expected.
  3. Post-Deploy Register: Post-deploy the Register component by checking the AKS workloads and verifying that the daemon set is running as expected.
  4. Post-Deploy Auditlog: Post-deploy the Auditlog component by checking the AKS workloads and verifying that the container app and function app are running as expected.

Go Grab a Coffee

Take a break and grab a cup of coffee. You've earned it!

Wednesday

Deploy All Components to TT02

The next step is to deploy all components to TT02 (Test Environment 02). This involves deploying the following components:

  • Authentication: This component is responsible for handling user authentication and authorization.
  • Resource Registry: This component is responsible for managing resources and their associated metadata.
  • Register: This component is responsible for registering new resources and updating existing ones.
  • Auditlog: This component is responsible for logging and auditing all changes made to the system.

To deploy these components, follow these steps:

  1. Deploy Authentication: Deploy the Authentication component to TT02 by clicking on the blue production chip and approving the pending release.
  2. Deploy Resource Registry: Deploy the Resource Registry component to TT02 by clicking on the blue production chip and approving the pending release.
  3. Deploy Register: Deploy the Register component to TT02 by clicking on the blue production chip and approving the pending release.
  4. Deploy Auditlog: Deploy the Auditlog component to TT02 by clicking on the blue production chip and approving the pending release.

Deploy Updates to APIM

The next step is to deploy updates to APIM (Azure API Management). This involves checking for updates to the following products:

  • #resourceregistry
  • #authentication
  • #register

If none of these products have been updated in the last week, no changes are needed. Otherwise, run the APIM TT02 pipeline and select the product that needs to be updated.

Post-Deploy All Components in TT02

After deploying all components to TT02, the next step is to post-deploy all components in TT02. This involves checking the AKS workloads for each component and verifying that they are running as expected.

  1. Post-Deploy Authentication: Post-deploy the Authentication component by checking the AKS workloads and verifying that the daemon set is running as expected.
  2. Post-Deploy Resource Registry: Post-deploy the Resource Registry component by checking the AKS workloads and verifying that the daemon set is running as expected.
  3. Post-Deploy Register: Post-deploy the Register component by checking the AKS workloads and verifying that the daemon set is running as expected.
  4. Post-Deploy Auditlog: Post-deploy the Auditlog component by checking the AKS workloads and verifying that the container app and function app are running as expected.

Go Grab a Coffee

Take a break and grab a cup of coffee. You've earned it!

Thursday

Go Through All GitHub Pull-Requests from Dependency Bots in All Repos

The final step is to go through all GitHub pull-requests from dependency bots in all repos. This involves checking the following repos:

  • Authentication
  • Authentication UI
  • Resource Registry
  • Register
  • Auditlog
  • Authorization Utils

To do this, follow these steps:

  1. Check Authentication: Check the Authentication repo for any pending pull-requests from dependency bots.
  2. Check Authentication UI: Check the Authentication UI repo for any pending pull-requests from dependency bots.
  3. Check Resource Registry: Check the Resource Registry repo for any pending pull-requests from dependency bots.
  4. Check Register: Check the Register repo for any pending pull-requests from dependency bots.
  5. Check Auditlog: Check the Auditlog repo for any pending pull-requests from dependency bots.
  6. Check Authorization Utils: Check the Authorization Utils repo for any pending pull-requests from dependency bots.

By following these steps, you can ensure that all components are deployed and patched correctly, and that all dependencies are up-to-date.

=====================================

Q: What is the purpose of deploying all components to production?

A: The purpose of deploying all components to production is to ensure that all components are running with the latest updates and patches. This helps to prevent any security vulnerabilities and ensures that the system is running smoothly.

Q: What are the components that need to be deployed to production?

A: The components that need to be deployed to production are:

  • Authentication: This component is responsible for handling user authentication and authorization.
  • Resource Registry: This component is responsible for managing resources and their associated metadata.
  • Register: This component is responsible for registering new resources and updating existing ones.
  • Auditlog: This component is responsible for logging and auditing all changes made to the system.

Q: How do I deploy the components to production?

A: To deploy the components to production, follow these steps:

  1. Deploy Authentication: Deploy the Authentication component to production by clicking on the blue production chip and approving the pending release.
  2. Deploy Resource Registry: Deploy the Resource Registry component to production by clicking on the blue production chip and approving the pending release.
  3. Deploy Register: Deploy the Register component to production by clicking on the blue production chip and approving the pending release.
  4. Deploy Auditlog: Deploy the Auditlog component to production by clicking on the blue production chip and approving the pending release.

Q: What is the purpose of deploying updates to APIM?

A: The purpose of deploying updates to APIM (Azure API Management) is to ensure that the API is running with the latest updates and patches. This helps to prevent any security vulnerabilities and ensures that the API is running smoothly.

Q: How do I deploy updates to APIM?

A: To deploy updates to APIM, follow these steps:

  1. Check for updates: Check for updates to the following products:
    • #resourceregistry
    • #authentication
    • #register
  2. Run the APIM prod pipeline: Run the APIM prod pipeline and select the product that needs to be updated.

Q: What is the purpose of post-deploying all components in production?

A: The purpose of post-deploying all components in production is to ensure that all components are running as expected after deployment. This involves checking the AKS workloads for each component and verifying that they are running as expected.

Q: How do I post-deploy all components in production?

A: To post-deploy all components in production, follow these steps:

  1. Post-Deploy Authentication: Post-deploy the Authentication component by checking the AKS workloads and verifying that the daemon set is running as expected.
  2. Post-Deploy Resource Registry: Post-deploy the Resource Registry component by checking the AKS workloads and verifying that the daemon set is running as expected.
  3. Post-Deploy Register: Post-deploy the Register component by checking the AKS workloads and verifying that the daemon set is running as expected.
  4. Post-Deploy Auditlog: Post-deploy the Auditlog component by checking the AKS workloads and verifying that the container app and function app are running as expected.

Q: What is the purpose of going through all GitHub pull-requests from dependency bots in all repos?

A: The purpose of going through all GitHub pull-requests from dependency bots in all repos is to ensure that all dependencies are up-to-date and that there are no security vulnerabilities.

Q: How do I go through all GitHub pull-requests from dependency bots in all repos?

A: To go through all GitHub pull-requests from dependency bots in all repos, follow these steps:

  1. Check Authentication: Check the Authentication repo for any pending pull-requests from dependency bots.
  2. Check Authentication UI: Check the Authentication UI repo for any pending pull-requests from dependency bots.
  3. Check Resource Registry: Check the Resource Registry repo for any pending pull-requests from dependency bots.
  4. Check Register: Check the Register repo for any pending pull-requests from dependency bots.
  5. Check Auditlog: Check the Auditlog repo for any pending pull-requests from dependency bots.
  6. Check Authorization Utils: Check the Authorization Utils repo for any pending pull-requests from dependency bots.

By following these steps, you can ensure that all components are deployed and patched correctly, and that all dependencies are up-to-date.