Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Local QA Environments #6594

Closed
1 task done
dansiegel opened this issue Nov 3, 2024 · 2 comments
Closed
1 task done

Support Local QA Environments #6594

dansiegel opened this issue Nov 3, 2024 · 2 comments
Labels
area-integrations Issues pertaining to Aspire Integrations packages untriaged New issue has not been triaged

Comments

@dansiegel
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Currently resources such as Azure SqlServer and Azure Storage run as local containers in development but when deploying these are excluded from the manifest and the actual Azure services are utilized. We need better support so that development teams can make local non-debug deployments which still utilize these containers so that QA can be done locally before PRs are merged and CI deploys to Azure.

Describe the solution you'd like

builder.AddAzureSqlServer("sql-server")
    .PreserveContainer(builder.Environment == "QA");

Additional context

No response

@joperezr joperezr added untriaged New issue has not been triaged area-integrations Issues pertaining to Aspire Integrations packages labels Nov 4, 2024
@joperezr
Copy link
Member

joperezr commented Nov 6, 2024

Discuss this during Triage. Currently, the default answer for doing this would either be having the QA team clone the project and run F5, or alternatively deploy to a staging environment that QA can use for testing. Is that something that can work for your use-case?

@joperezr joperezr added the needs-author-action An issue or pull request that requires more info or actions from the author. label Nov 6, 2024
@dansiegel
Copy link
Author

Discuss this during Triage. Currently, the default answer for doing this would either be having the QA team clone the project and run F5, or alternatively deploy to a staging environment that QA can use for testing. Is that something that can work for your use-case?

Sorry I had missed your reply @joperezr. Running local isn't really an issue at all.. but for a local staging environment the concern would be to be able to deploy to another machine. The concern here would be to consider that you still want local Docker Resources for things like SQL Server, Storage, etc... that would normally be split off into actual provisioned Azure Resources. TBH I haven't had a chance to really dig into Aspir8, I'm not sure if perhaps the answer here would be that it could be part such a solution.

@dotnet-policy-service dotnet-policy-service bot removed no-recent-activity needs-author-action An issue or pull request that requires more info or actions from the author. labels Nov 27, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Dec 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-integrations Issues pertaining to Aspire Integrations packages untriaged New issue has not been triaged
Projects
None yet
Development

No branches or pull requests

2 participants