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
***starter:**`entra_username` not required ([e8ef978](https://github.com/Keyfactor/actions/commit/e8ef978040b927afe117590e13034ed37c7aa7a4))
7
-
***starter:** Call out `write` permissions on generate-readme ([578161c](https://github.com/Keyfactor/actions/commit/578161ce9288a0b2047854dd499b96996ee75bb6))
8
-
***starter:** Remove container and maven workflow refs. ([86dfcf4](https://github.com/Keyfactor/actions/commit/86dfcf41593fbc3562baea46d6590079f328559f))
***starter:** Update self refs for generate-readme ([5858ee9](https://github.com/Keyfactor/actions/commit/5858ee9f1653ec153ad3297d21cdc9aa5b4d42e5))
11
-
***starter:** Update self version references from `v3` to `v4` ([79bd7a4](https://github.com/Keyfactor/actions/commit/79bd7a4ba43e3a8a94552872e51174402c2bd8b2))
* The v4 Actions make use of [doctool](https://github.com/Keyfactor/doctool) to take Command screenshots for Universal Orchestrator extension store-type creation.
4
+
5
+
* The v4 Actions make use of [doctool](https://github.com/Keyfactor/doctool) to take Command screenshots for Universal
6
+
Orchestrator extension store-type creation.
5
7
6
8
### Usage
7
9
8
10
#### Prerequisites
9
-
- Ensure an `integration-manifest.json` file is present in the root of your repository. For the schema, see the v2 [integration-manifest-schema.json](https://keyfactor.github.io/v2/integration-manifest-schema.json)
11
+
12
+
- Ensure an `integration-manifest.json` file is present in the root of your repository. For the schema, see the
"description": "Username for the CA API service account"
35
-
},
36
-
{
37
-
"name": "Password",
38
-
"description": "Password for the CA API service account"
39
-
},
40
-
{
41
-
"name": "BaseUrl",
42
-
"description": "The Base URL for the CA API"
43
-
},
44
-
{
45
-
"name": "Enabled",
46
-
"description": "Flag to Enable or Disable gateway functionality. Disabling is primarily used to allow creation of the CA prior to configuration information being available."
47
-
}
48
-
],
49
-
"enrollment_config": [
50
-
{
51
-
"name": "CertificateValidityInYears",
52
-
"description": "Number of years the certificate will be valid for"
53
-
},
54
-
{
55
-
"name": "Email",
56
-
"description": "Email address of the requestor"
57
-
},
58
-
{
59
-
"name": "OrganizationName",
60
-
"description": "Name of the organization to be validated against"
"description": "Username for the CA API service account"
40
+
},
41
+
{
42
+
"name": "Password",
43
+
"description": "Password for the CA API service account"
44
+
},
45
+
{
46
+
"name": "BaseUrl",
47
+
"description": "The Base URL for the CA API"
48
+
},
49
+
{
50
+
"name": "Enabled",
51
+
"description": "Flag to Enable or Disable gateway functionality. Disabling is primarily used to allow creation of the CA prior to configuration information being available."
52
+
}
53
+
],
54
+
"enrollment_config": [
55
+
{
56
+
"name": "CertificateValidityInYears",
57
+
"description": "Number of years the certificate will be valid for"
58
+
},
59
+
{
60
+
"name": "Email",
61
+
"description": "Email address of the requestor"
62
+
},
63
+
{
64
+
"name": "OrganizationName",
65
+
"description": "Name of the organization to be validated against"
66
+
}
67
+
],
68
+
"product_ids": [
69
+
"ExampleProductSslOvBasic",
70
+
"ExampleProductSslEvBasic",
71
+
"ExampleProductSslDvGeotrust",
72
+
"ExampleProductSslDvThawte",
73
+
"ExampleProductSslOvThawteWebserver",
74
+
"ExampleProductSslEvThawteWebserver",
75
+
"ExampleProductSslOvGeotrustTruebizid",
76
+
"ExampleProductSslEvGeotrustTruebizid",
77
+
"ExampleProductSslOvSecuresite",
78
+
"ExampleProductSslEvSecuresite",
79
+
"ExampleProductSslOvSecuresitePro",
80
+
"ExampleProductSslEvSecuresitePro"
81
+
]
78
82
}
83
+
}
79
84
}
80
85
```
81
86
82
87
#### Example workflow `keyfactor-bootsrap-workflow.yml`
* Run the workflows and conditionalized steps to produce a build. If conditions match, release artifacts are delivered
121
-
[dotnet-build-and-release.yml](.github/workflows/dotnet-build-and-release.yml) or [go-build-and-release.yml](.github/workflows/go-build-and-release.yml)
122
-
workflow will be run depending on the `detected-primary-language` step in [starter.yml](.github/workflows/starter.yml)
or [go-build-and-release.yml](.github/workflows/go-build-and-release.yml)
147
+
workflow will be run depending on the `detected-primary-language` step in [starter.yml](.github/workflows/starter.yml)
123
148
124
149
#### On Create:
125
-
* Configure repository settings - This will use the properties from the json to update topic and description, and will set the teams permissions on the repo accordingly. If the ref created is a branch that matches "release-\*.\*", branch protection is added, autlink reference set ab# to devops [***kf-configure-repo***]
150
+
151
+
* Configure repository settings - This will use the properties from the json to update topic and description, and will
152
+
set the teams permissions on the repo accordingly. If the ref created is a branch that matches "release-\*.\*", branch
153
+
protection is added, autlink reference set ab# to devops [***kf-configure-repo***]
126
154
127
155
#### On push or workflow_dispatch:
156
+
128
157
* Just run the build on the branch with the commit without producing release artifacts
129
-
* * C#: run the [dotnet-build-and-release.yml](.github/workflows/dotnet-build-and-release.yml) workflow
130
-
* * Go builds: run the go-build-and-release.yml workflow (still in progress)
131
-
* All languages:
132
-
* * Generate/Update `README.md` using `doctool` [generate-readme.yml](.github/workflows/generate-readme.yml)
133
-
* * (conditionally) a catalog entry [update-catalog](.github/workflows/update-catalog.yml) will be created/updated if the json manifest has `"update_catalog": true` in the `integration-manifest.json` file
158
+
*
159
+
* C#: run the [dotnet-build-and-release.yml](.github/workflows/dotnet-build-and-release.yml) workflow
160
+
*
161
+
* Go builds: run the go-build-and-release.yml workflow (still in progress)
162
+
* All languages:
163
+
*
164
+
* Generate/Update `README.md` using `doctool`[generate-readme.yml](.github/workflows/generate-readme.yml)
165
+
*
166
+
* (conditionally) a catalog entry [update-catalog](.github/workflows/update-catalog.yml) will be created/updated if
167
+
the json manifest has `"update_catalog": true` in the `integration-manifest.json` file
134
168
135
169
#### On pull_request[opened, closed, synchronize, edited, reopened]:
136
-
[dotnet-build-and-release.yml](.github/workflows/dotnet-build-and-release.yml) workflow or [go-build-and-release.yml](.github/workflows/go-build-and-release.yml) workflow will be run depending on the detected primary language
137
-
* If the pr destination is a `release-*.*` branch, set flags to produce release artifacts
138
-
* If the pr is determined to be `open` or `merged` but not `closed` (synchronize), a prerelease artifact will be uploaded
139
-
* If the pr is determined to be `merged` and `closed`, a final "official" release is built and published to GitHub releases, and if `"update_catalog": true` is set in the json manifest, a catalog entry will be created/updated
140
-
* Polaris SAST/SCAN scans run when push to `release-*` or main occurs
141
-
* If PR to release branch is `merged/closed`, a new PR will be automatically generated. This will need to be approved manually and **should not** be approved for hotfix branches
0 commit comments