You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Eliminates the Terraform workflow for remote state setup, which is no longer needed.
Updates documentation to clarify the configuration for GitHub runners, ensuring users have accurate guidance for setting up and using self-hosted runners effectively.
This streamlines the CI/CD process and removes potential confusion for new users.
Update Gitleaks scanning for newly initialized templates with no remote branch set.
update gitignore to avoid including sensitive data in cicd/.ssh/
cicd/.ssh/* as terraform backend and GH runner code will be executed locally per the updated guidance
* feat: add Azure Developer CLI Assistant Mode documentation
* feat: add GitHub CLI feature to devcontainer and update documentation for CI/CD setup
Adds GitHub CLI feature to devcontainer and enhances CI/CD docs
Introduces the GitHub CLI feature into the development container, improving the setup for developers.
Updates documentation to streamline the CI/CD pipeline configuration, enhancing user guidance for Azure Developer CLI workflows.
This change aims to facilitate easier project initialization and deployment processes.
* dd additional API permissions guidance for service principal in azd-assistant documentation
* update GitHub runner configuration and registration token handling in documentation
* remove azd copilot chat mood file into a separate PR
* fix: remove trailing comma from GitHub runner configuration in README
* Update docs/cicd.md
grammar updates
Co-authored-by: Ian Jensen <[email protected]>
* Update docs/cicd.md
typo
Co-authored-by: Ian Jensen <[email protected]>
* Update docs/cicd.md
wording
Co-authored-by: Ian Jensen <[email protected]>
---------
Co-authored-by: Ian Jensen <[email protected]>
@@ -161,6 +167,7 @@ A related option is VS Code Dev Containers, which will open the project in your
161
167
```
162
168
163
169
Note that this command will initialize a git repository, so you do not need to clone this repository.
170
+
This will also create a new folder with the environment name you entered though the cmd steps in the `.azure` folder. It will also set it as the default environment for any calls to `azd` going forward.
164
171
165
172
### Deploying
166
173
@@ -181,14 +188,6 @@ The steps below will provision Azure and Power Platform resources and will deplo
181
188
182
189
*Note: the `pac auth create` command may return a warning about being unable to connect to a Dataverse organization. This is expected, and will not impact the deployment.*
183
190
184
-
1. Create a new azd environment:
185
-
186
-
```shell
187
-
azd env new
188
-
```
189
-
190
-
This will create a new folder in the `.azure` folder, and set it as the active environment for any calls to `azd` going forward.
191
-
192
191
1. Set you internative testing user.
193
192
194
193
```shell
@@ -197,7 +196,7 @@ The steps below will provision Azure and Power Platform resources and will deplo
197
196
198
197
Set this value to the Azure Entra ID object ID of the primary administrator or developer who will manage and modify the deployed solution resources in the future. This user will be granted administrative access to the Power Platform resources (such as bot ownership and environment management) and will have visibility into the Azure resources provisioned by this deployment. Replace `entraid_user_object_id` with the actual object ID of the intended admin or developer.
After deployment, use the output values to configure your Terraform backend in other projects:
55
+
After deployment, use the output to set the remote state values for your template.
54
56
55
57
```hcl
56
-
terraform {
57
-
backend "azurerm" {
58
-
storage_account_name = "sttfstate<random>"
59
-
container_name = "tfstate"
60
-
key = "terraform.tfstate"
61
-
resource_group_name = "rg-tfstate-<random>"
62
-
subscription_id = "your-subscription-id"
63
-
use_azuread_auth = true
64
-
}
58
+
backend_config = {
59
+
"container_name" = "CONTAINER_NAME"
60
+
"resource_group_name" = "RESOURCE_GROUP_NAME"
61
+
"storage_account_name" = "STORAGE_ACCOUNT_NAME"
62
+
"subscription_id" = "SUBSCRIPTION_ID"
65
63
}
66
64
```
67
65
66
+
```shell
67
+
# Set the remote state variables
68
+
azd env set RS_STORAGE_ACCOUNT 'STORAGE_ACCOUNT_NAME'
69
+
azd env set RS_CONTAINER_NAME 'CONTAINER_NAME'
70
+
azd env set RS_RESOURCE_GROUP 'RESOURCE_GROUP_NAME'
71
+
72
+
# Direct jobs to the new runner by setting a repo variable used by your workflows for `runs-on` selection
73
+
azd env set ACTIONS_RUNNER_NAME ['self-hosted']
74
+
75
+
# Update the template to use remote backend
76
+
azd hooks run prepackage
77
+
```
78
+
79
+
- `ACTIONS_RUNNER_NAME`: set to `['self-hosted']` (JSON array syntax) to target any self-hosted runner
80
+
81
+
Note: The runner VM registers with labels like `self-hosted,vm,<resource-group>,<location>,<unique-id>`. You can narrow job placement further by including those additional labels in your `runs-on` matrix if desired.
82
+
68
83
## Security Features
69
84
70
85
- Private storage account (no public access)
@@ -81,16 +96,5 @@ This configuration automatically sets up GitHub repository variables for CI/CD p
81
96
- `RS_RESOURCE_GROUP`: Name of the resource group containing the storage account
82
97
- `RS_CONTAINER_NAME`: Name of the storage container for Terraform state
83
98
84
-
These variables can be used in GitHub Actions workflows to configure Terraform backend settings.
85
-
86
-
## Environment Variables Alternative
99
+
These variables will be used in GitHub Actions workflows to configure Terraform backend settings.
87
100
88
-
Instead of using `terraform.tfvars.json`, you can set environment variables:
0 commit comments