azure-samples / apptemplate-wordpress-on-aca Goto Github PK

Once issue #2 is addressed, instead of git clone and then azd init. you can just do azd up -t apptemplate-wordpress-aca

Describe the issue:
After providing required value as repository secrets to be used by the GitHub Actions workflow, execute the azure-dev.yml action workflow.
The following error was encountered.

Repro Steps:

1. Fork the repository https://github.com/Azure-Samples/apptemplate-wordpress-on-aca.
2. Create an Azure Service Principal.
3. Store the required value as GitHub Actions secrets.
4. Execute the azure-dev.yml action workflow.

Expected behavior:
Workflow can deploy resources normally.

@kpantos for notification.

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Follow all steps up to and then run az provision

Any log messages given by the failure

Expected/desired behavior

Provision complete successfully.

OS and Version?

Windows 11

Mention any other details that might be useful

Please provide us with the following information:

This issue is for a: (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Fork the main branch as instructed and follow the documentation steps to create secrets and variables
Run WordPress Deployment

Any log messages given by the failure

25s
Run Azure/cli@v1
with:
azcliversion: 2.45.0
inlineScript: az deployment sub what-if
--location westeurope
--template-file ./infra/main.bicep
--parameters environmentName=prod
--parameters location=westeurope
--parameters fqdn=http://mysite.com
--parameters applicationName=reponame
--parameters mariaDBPassword=***
--parameters adminUsername=myadmin
--parameters adminPassword=***
--parameters redisDeploymentOption=container

env:
AZURE_HTTP_USER_AGENT:
AZUREPS_HOST_ENVIRONMENT:
Starting script execution via docker image mcr.microsoft.com/azure-cli:2.45.0
/home/runner/work/_temp/AZ_CLI_GITHUB_ACTION_1699465613547.sh: line 9: ***: command not found
Error: Error: az cli script failed.
cleaning up container...
MICROSOFT_AZURE_CLI_1699465613320_CONTAINER

Error: az cli script failed.

Expected/desired behavior

I expected the deploy to finish with success

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Windows 11

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

azd includes all outputs in .env after a customer runs azd up or azd provision. If you add all the outputs, customers do not need to manually edit the following:

AZD_PIPELINE_PROVIDER="github"
AZURE_ADMIN_PASSWORD="<THE JUMPHOST PASSWORD>"
AZURE_ADMIN_USERNAME="<THE JUMPHOST USERNAME>"
AZURE_APPLICATION_NAME="<AN APPLICATION NAME>"
AZURE_ENV_NAME="prod"
AZURE_FQDN="<THE FQDN OF THE SITE>"
AZURE_LOCATION="<AN AZURE DC REGION>"
AZURE_MARIADB_PASSWORD="<THE MARIADB PASSWORD>"
AZURE_PRINCIPAL_ID=""
AZURE_SUBSCRIPTION_ID="<YOUR AZURE SUBSCRIPTION ID>"
resourceGroupName="<THE RESOURCE GROUP NAME>"

Also, if default value is not found for a parameter, azd will prompt customer for input.

1. e.g., add in main.bicep,
   output AZURE_ADMIN_USERNAME string = adminUsername
2. For consistent - rename resourceGroupName to AZURE_RESOURCE_GROUP.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [X ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

In alignment with the Azure Database for MariaDB retirement announcement, we stopped support for creating MariaDB instances via the Azure portal or CLI as of March 19, 2024.
https://learn.microsoft.com/en-us/azure/mariadb/whats-happening-to-mariadb

Any log messages given by the failure

Deployment Error Details: InvalidElasticServerType: The provided server type value 'Azure Database for MariaDB - Single Server' is invalid.

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

As we discovered when we met. Logging a bug to track this.

Saw the allowed regions in main.bicep, for azd, it may be good to list the allowed regions out in the readme. The first time I tried deploying this template using azd, deployment failed. Think it was because I picked a region that is not supported by ACA.

Describe the issue:
When executing the azd provision command, provisioning resource failed.

Repro Steps:

1. azd init -t <template_name>
2. azd package
3. azd provision with deployWithRedis is off (Enter a random string when prompted)
   
4. azd provision with deployWithRedis is on (Enter a random string when prompted)
   

Notes: Are we randomly entering a string based on the prompt? Or where to get these special values?

Environment:
OS: Windows
Azd version: azd version 0.8.0-beta.1-daily.2689578 (commit 3b28fc8f84717d732f646a3e3b9521204f122112)

Expected behavior:
Executing azd provision can pass.

@rajeshkamal5050, @kpantos for notification.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

We are updating this template to support new features in Github Action.

The az cli is used to sign in to Azure and deploy resources in the github workflow of this pr. Do we need to modify it to azd cli?

@kpantos , @rajeshkamal5050, @aarthiem for notification.