-
Notifications
You must be signed in to change notification settings - Fork 94
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
Issue in documentation for Deploying Aspire via AZDO #983
Comments
Hello, if you run |
Another annoyance: AZD_INITIAL_ENVIRONMENT_CONFIG is set to secret when the pipeline is pushed to my project. I can't validate whether anything in this variable is correct. This would be less problematic if it was pushed as a normal var and let the user set it as secret. Once it's a secret it can't be viewed. |
Hey @alexwolfmsft - any chance you could look into this one? |
I have the same issue. Set everything up with azd init. Created DEV environment and pushing to it successfully with azd up. When development got to the point we wanted to add CI/CD we just faced a wall. Documentation prescribed steps produce a pipeline in our Azure DevOps organization, but when the pipeline is running - it just returns: Provision infrastructure step ERROR: no project exists; to create a new project, run I can only assume that developers are not using Azure DevOps themselves and documentation is even contains an image with a sample of the setup command using GitHub actions for Azure DevOps section: https://learn.microsoft.com/en-us/dotnet/aspire/deployment/azure/aca-deployment-github-actions?tabs=windows&pivots=azure-pipelines#create-the-azure-devops-repository-and-pipeline It's not a "sample app" for some of us. We're trying to get to market fast with a small team, however we're stumbling over smallest things all the time, because Aspire is not treated as an enterprise level solution it seems. |
So is no one going to look at this? I put it aside for a while because I was solo so I could just manually deploy, but now I'm building an MVP. I brought on a 20+ year .NET developer / architect and he can't get it to work either. My initial message was almost 6 months ago! |
cc @vhvb1989 |
@joseph-hungerman , since you ran azd init from inside the AppHost folder, the azure.yaml is created there. On your pipeline, either use the cwd for the step where you are running azd provision or manually cd into your AppFolder before running azd provision. You are not expected to run azd init on CI/CD Lmk if this works for you. (Optionally, you can use the root of your repo to run azd init and then you wouldn't need to cd to the AppHost folder on CI/CD) |
So moving azure.yaml to the root of the solution worked, after I updated the directory. All of the documentation I have see says to run azd init on the project. So that probably needs to be looked at. Now I am facing an issue in deploy pulling env vars I have setup in the .env file for the Testing environment. I have all of the files as secure files, and the variables are setup in a group within the library. I have checked and the file is being downloaded to where I expect. Here is my pipeline and the error: `
pool: variables: steps:
- task: AzureCLI@2displayName: Provision Infrastructureinputs:azureSubscription: azconnectionscriptType: bashscriptLocation: inlineScriptinlineScript: |azd provision --no-prompt --environment $(AZURE_ENV_NAME)env:AZURE_SUBSCRIPTION_ID: $(AZURE_SUBSCRIPTION_ID)AZURE_ENV_NAME: $(AZURE_ENV_NAME)AZURE_LOCATION: $(AZURE_LOCATION)
ERROR: failed deploying service 'cache': failed executing template file: template: manifest template:2:17: executing "manifest template" at <.Env.AZURE_LOCATION>: map has no entry for key "AZURE_LOCATION" Cache template:
|
I am attempting to deploy an Aspire app to Azure. I followed the documentation and everything went as expected until I reached the provisioning step of the Pipeline. I get an error back that says: ERROR: no project exists; to create a new project, run
azd init
. I ran this command as stated within the documentation, which creates a set of documents that are ignored by the repo. I am assuming this config is set within the connection of the pipeline workflow and creating the pipeline using bicep. I tried running the following pwsh command, but there is a prompt to continue that has no default, so this option didn't work. I then tried exposing the .azure folder to git and that didn't work either. Some help troubleshooting this would be great. I would also expect this to be covered within the documentation.- pwsh: | azd init --environment $(AZURE_ENV_NAME) --location $(AZURE_LOCATION) --subscription $(AZURE_SUBSCRIPTION_ID) --from-code --no-prompt
The text was updated successfully, but these errors were encountered: