Skip to content

Conversation

eerhardt
Copy link
Member

@eerhardt eerhardt commented Nov 15, 2024

  • Ensure any "known" parameters used by the infrastructure are in the Aspire AzureBicepResource's Parameter list
  • Remove unnecessary duplicate parameter manipulation

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
  • Did you add public API?
    • No
  • Does the change make any security assumptions or guarantees?
    • No
  • Does the change require an update in our Aspire docs?
    • No
Microsoft Reviewers: Open in CodeFlow

Base automatically changed from RefactorEntryAndKeyAuth to main November 18, 2024 20:45
- Ensure any "known" parameters used by the infrastructure are in the Aspire AzureBicepResource's Parameter list
- Remove unnecessary duplicate parameter manipulation
@eerhardt eerhardt enabled auto-merge (squash) November 19, 2024 21:12
@eerhardt eerhardt merged commit 2213dfc into main Nov 19, 2024
9 checks passed
@eerhardt eerhardt deleted the ParameterRefactor branch November 19, 2024 21:23
eerhardt added a commit to eerhardt/aspire that referenced this pull request Nov 22, 2024
With Refactor Bicep parameter usage (dotnet#6683), we changed when "well-known" parameters were added to the AzureBicepResource. Instead of adding them up front in 2 places, we add them during bicep generation (i.e. ConfigureInfrastructure) and then sync the bicep parameters back to Aspire's AzureBicepResource.Parameters.

This broke Azure Provisioning because it is looking for well known parameters before GetBicepTemplateFile is called. It needs to populate the well-known parameters after.

The fix is to move the calls around so PopulateWellKnownParameters is called after GetBicepTemplateFile.
@eerhardt eerhardt mentioned this pull request Nov 22, 2024
5 tasks
eerhardt added a commit that referenced this pull request Nov 25, 2024
With Refactor Bicep parameter usage (#6683), we changed when "well-known" parameters were added to the AzureBicepResource. Instead of adding them up front in 2 places, we add them during bicep generation (i.e. ConfigureInfrastructure) and then sync the bicep parameters back to Aspire's AzureBicepResource.Parameters.

This broke Azure Provisioning because it is looking for well known parameters before GetBicepTemplateFile is called. It needs to populate the well-known parameters after.

The fix is to move the calls around so PopulateWellKnownParameters is called after GetBicepTemplateFile.
@github-actions github-actions bot locked and limited conversation to collaborators Dec 20, 2024
@github-actions github-actions bot added the area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication label Mar 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-app-model Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants