kovagoadi/hunfabric
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename new botstrap stage to org-setup (#3299)

Browse Source 
* readme changes

* rename stage 0

* rename stage 0

* complete rename of stage 0

* tfdoc

* tfdoc

* tfdoc
This commit is contained in:
Ludovico Magnocavallo
2025-09-04 13:34:16 +02:00
committed by GitHub
parent bc6950e205
commit 756c02c21a
118 changed files with 334 additions and 348 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
fast/extras/0-cicd-github/README.md
View File

@@ -94,7 +94,7 @@ repositories = {
issues = true
}
}
populate_from = "../../stages/0-bootstrap"
populate_from = "../../stages/0-org-setup"
}
fast_01_resman = {
create_options = {
@@ -127,7 +127,7 @@ repositories = {
issues = true
}
}
populate_from = "../../stages/0-bootstrap"
populate_from = "../../stages/0-org-setup"
populate_samples = true
}
fast_01_resman = {

17
fast/extras/0-cicd-gitlab/README.md
View File

@@ -28,8 +28,8 @@ Gitlab hostname and SSH port on the `gitlab_config` section.
### Gitlab Config
The `gitlab_config` variable defines where projects will be hosted.
GitLab can either be the SaaS offering (with the default hostname `gitlab.com`)
or a self-hosted instance with a custom FQDN. If hostname is set to gitlab.com, you must
GitLab can either be the SaaS offering (with the default hostname `gitlab.com`)
or a self-hosted instance with a custom FQDN. If hostname is set to gitlab.com, you must
also set the `saas_group` variable to specify the group path where resources will be created.
This is an example that configures a SaaS gitlab instance using `my_group/gcp` as default group :
@@ -157,7 +157,7 @@ projects = {
}
}
group = "org-admins"
populate_from = "../../stages/0-bootstrap"
populate_from = "../../stages/0-org-setup"
workflow_file = "bootstrap-workflow.yaml"
}
fast_01_resman = {
@@ -211,7 +211,7 @@ projects = {
}
}
group = "org-admins"
populate_from = "../../stages/0-bootstrap"
populate_from = "../../stages/0-org-setup"
populate_sample = true
workflow_file = "bootstrap-workflow.yaml"
}
@@ -266,7 +266,7 @@ projects = {
}
}
group = "org-admins"
populate_from = "../../stages/0-bootstrap"
populate_from = "../../stages/0-org-setup"
populate_sample = true
workflow_file = "bootstrap-workflow.yaml"
}
@@ -348,7 +348,7 @@ An optional variable `commit_config` can be used to configure the author, email,
and message used in commits for the initial population of files. Its defaults
are probably fine for most use cases.
## How to run this stage:
## How to run this stage
Connect to Gitlab as root user and create a personal access token with permissions as per the [gitlab provider credentials](#gitlab-provider-credentials).
Set the newly created personal access as `gitlab_config.access_token` variable
@@ -358,11 +358,11 @@ and then issue the following commands:
gcloud storage cp gs://${prefix}-prod-iac-core-outputs-0/workflows/*-workflow.yaml ./workflows/
```
This will download Gitlab CICD workflow files generated during 0-bootstrap stage
This will download Gitlab CICD workflow files generated during 0-org-setup stage
on the local .workflows directory for later being uploaded on the new Gitlab
projects.
Set `http_proxy` and `https_proxy` env vars to http://localhost:3128 and then
Set `http_proxy` and `https_proxy` env vars to <http://localhost:3128> and then
run:
```bash
@@ -386,7 +386,6 @@ terraform init.
Try to create a merge request to trigger a CI pipeline on one of FAST stages and
check if the plan pipeline executes successfully.
<!-- TFDOC OPTS files:1 -->
<!-- BEGIN TFDOC -->
## Files