Adding images
@ -173,7 +173,7 @@ Secret Name|Description|Example
|
||||
|
||||
When you are done, the secrets should look something like this:
|
||||
|
||||

|
||||

|
||||
**Figure 1**: Repository secrets.
|
||||
|
||||
### Check workflows for the Catalog API
|
||||
@ -184,20 +184,20 @@ Ensure that you see `catalog-api` and `Deploy catalog-api` in the list of workfl
|
||||
|
||||
You can test that the workflow is working correctly by selecting the `catalog-api` workflow. Next, select **Run workflow** to manually trigger the workflow. Select the `dev` branch.
|
||||
|
||||

|
||||

|
||||
**Figure 2**: Triggering the catalog-api workflow manually.
|
||||
|
||||
Make sure that the `catalog-api` workflow completes successfully, which should in turn trigger the `Deploy catalog-api` workflow. Ensure that this workflow completes successfully too.
|
||||
|
||||

|
||||

|
||||
**Figure 3**: Catalog-api successful run.
|
||||
|
||||

|
||||

|
||||
**Figure 4**: Deploy catalog-api successful run.
|
||||
|
||||
Ensure that you can [navigate to the store front](https://github.com/dotnet-architecture/eShopOnContainers/wiki/Deploy-to-Azure-Kubernetes-Service-(AKS)#explore-eshoponcontainers) using the ingress URLs. Take note of the names of the first few items:
|
||||
|
||||

|
||||

|
||||
**Figure 5**: Store front displaying items.
|
||||
|
||||
## Release a code change
|
||||
@ -208,25 +208,25 @@ Now that you have verified that the build and deploy workflows are working, you
|
||||
|
||||
Navigate to `src/Services/Catalog/Catalog.API/Controllers/CatalogController.cs` on the `dev` branch. Scroll down to around line 63. Remove the comments `/*` and `*/` above and below the `foreach` loop:
|
||||
|
||||

|
||||

|
||||
**Figure 6**: Uncomment the for loop.
|
||||
|
||||
Scroll to the bottom of the page and commit the change directly to the `dev` branch, entering a commit message:
|
||||
|
||||

|
||||

|
||||
**Figure 7**: Commit the code change.
|
||||
|
||||
Select the **Actions** tab and ensure that a new workflow has triggered.
|
||||
|
||||

|
||||

|
||||
**Figure 8**: Workflow triggered by pushing to `dev`.
|
||||
|
||||
Once that workflow completes, you should see the deploy workflow trigger immediately:
|
||||
|
||||

|
||||

|
||||
**Figure 9**: Deploy workflow triggered after building completes.
|
||||
|
||||
After about a minute, navigate back to the store front and verify that the word `Awesome` appears in front of each catalog item:
|
||||
|
||||

|
||||

|
||||
**Figure 10**: ew code is running successfully.
|
BIN
images/Deployment-With-GitHub-Actions/awesome-items.jpg
Normal file
After Width: | Height: | Size: 176 KiB |
BIN
images/Deployment-With-GitHub-Actions/catalog-api-success.jpg
Normal file
After Width: | Height: | Size: 74 KiB |
BIN
images/Deployment-With-GitHub-Actions/code-commit.jpg
Normal file
After Width: | Height: | Size: 53 KiB |
After Width: | Height: | Size: 60 KiB |
After Width: | Height: | Size: 100 KiB |
BIN
images/Deployment-With-GitHub-Actions/repo-secrets.jpg
Normal file
After Width: | Height: | Size: 97 KiB |
BIN
images/Deployment-With-GitHub-Actions/store-before.jpg
Normal file
After Width: | Height: | Size: 145 KiB |
BIN
images/Deployment-With-GitHub-Actions/trigger-catalog-api.jpg
Normal file
After Width: | Height: | Size: 209 KiB |
BIN
images/Deployment-With-GitHub-Actions/uncomment-for.jpg
Normal file
After Width: | Height: | Size: 103 KiB |
BIN
images/Deployment-With-GitHub-Actions/workflow-triggered.jpg
Normal file
After Width: | Height: | Size: 124 KiB |