Azure-Samples / Azure-Samples/java-microservices-aks-lab
https://github.com/Azure-Samples/java-microservices-aks-lab/blob/main/docs/06_lab_events/0603.md
- Langage dominant
- Java
- Étoiles
- 11
- Forks
- 176
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
# Lab: 06
Description of issue - Items identified in QA
---
**- In Task 'Step by step guidance', Step 1:** I was unable to get the referenced 'az storage container create' command to work successfully, and unfortunately was unable to determine the root-cause for failure. Hopefully the CO can dig deeper for solution to this issue.
In order to proceed, I was able to easily create the storage account manually through the Azure UI.
See also identical issue in similar MicrosoftLearning course _Deploying-and-Running-Java-Applications-in-Azure-Spring-Apps_: https://github.com/MicrosoftLearning/Deploying-and-Running-Java-Applications-in-Azure-Spring-Apps/issues/40
---
**- In Task 'Step by step guidance', Step 3:** Text says:
`In the config repository you will need to add the configuration for receiving messages from the event hub. Replace the contents of the current application.yml file with the contents of the [0603_application.yml file](https://github.com/Azure-Samples/java-microservices-aks-lab/blob/main/docs/06_lab_events/0603_application.yml). Make sure you fill out your current MySQL server name on line 12 and the name of your event hub namespace on line 28.`
However, the numbering is off for MySQL server name - it appears to be line 48, and not line 12.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par docs/06_lab_events/0603.md, examinez l’étape 1 et l’étape 3, puis inspectez le fichier 0603_application.yml lié. Vérifiez la commande az storage container create et les numéros de ligne référencés pour le serveur MySQL et l’espace de noms de l’event hub ; la documentation est terminée lorsque les indications concernant la commande sont utilisables et que les références de ligne sont exactes.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- azure, java, kubernetes, mysql
- Domaine
- cloud, databases, documentation
- Type d'issue
- Documentation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 45/100