Deploy Pet-Clinic microservices using azd #48
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Support adding MySQL when run `azd init`
Fix typo by changing "DbMysql" to "DbMySql"
…or like this: "argetTypeNotSupported: Target resource type MICROSOFT.DBFORMYSQL/FLEXIBLESERVERS is not supported.".
2. Delete '1>&2' used for debug. 3. Add 'az tag create' to fix the problem about tag been deleted when creating service connector.
Use managed-identity instead of username and password
2. Update log about "failed to read spring application properties". 3. Fix bug about can not find frontend app and backend app at the same time. 4. Add service connector from aca to postgresql.
Use passwordless to connect to PostgreSQL in Azure Container Apps
Fix a bug within the for-loop for reverse infra generation mapping. The value should be referenced via pointer to persist modification.
…azure-javaee#27) * prompt if detected kafka but no spring-cloud-azure found, can help to add this dep * remove auto-add dep code * add UT * resolve comments * remove unused ones --------- Co-authored-by: haozhang <[email protected]>
…to hooks (Azure#4244) * service hooks * As part of merging azd operation and hooks, this PR allows users to define hooks outside of azure.yaml as individual files with the name azd.hooks.[yaml | yml]. The file can be placed in the /infra folder for project level hooks or inside service's folder for service level hooks. This will allow generators like Aspire to include hooks as part of the infrastructure code (w/o touching azure.yaml). Then, when running azd infra synth, the hooks are part of the infrastructure and users can delete the infra folder to go back to full Aspire in-memory generation w/o touching azure.yaml. After this PR, I am planning to move the azd operations to become a valid built-in hook and delete the alpha feature for azd operations and the entire feature in favor of just using the hooks strategy
…ing boot version (azure-javaee#28) * for Kafka, inject AzureEventHubsKafkaAutoConfiguration package path based on spring boot version * parse properties to fill possible spring boot version * update UT * update detect spring boot version logic * small fix --------- Co-authored-by: haozhang <[email protected]>
* 1. Fix error: Missing information in ServiceSpec. Like messaging service. 2. Use DatabaseMysql to replace DatabaseReference to make code simplifier. Same to all other db type. 3. Simplify the code of handleContainerAppProps. 4. Simplify the code of Frontend and Backend fulfill in ServiceSpec * Fix test error. * 1. Print hints about uses relationships. 2. Add frontend BASE_URL in backend service. * Delete "todo" because it's already done. * Use printf for each line of log to make it look better. * Use console.Message instead of log.Printf. Because log.Printf will print nothing when there is no "--debug" added when run azd. * Fix compile error in test files. * Update the description in hints. * 1. Split "mapUses" function into to functions: "mapUses" and "printHintsAboutUses". 2. Add missing hint for AI module.
The current version that is installed on the runners (0.31.34) has some bugs around linting and causes lint warnings during our legs. These errors are not present on the latest Bicep CLI. Force an upgrade of the binary that is installed as part of the test runner to latest version. We should be able to remove this step once new image is built with an upgraded bicep (the `README.md` at https://github.com/actions/runner-images/tree/main/images/ubuntu has information about what is on the runner.)
We should be able to re-enable the tests now. The one exception is the `azd login` test that validated login with a long lived client secret, since we no longer have a service principal with a long lived client secret. We'll have to make due without the end to end coverage here - but in practice we have good coverage at the unit test level of much of the code here, so we should be okay. Contributes To Azure#4564
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.