Skip to content

fix: airgap support #105

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.

Sign up for GitHub

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

Merged
merged 6 commits into from
Feb 28, 2025
Merged

fix: airgap support #105

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
198d2f9
chore: update airgap support
huayuenh Feb 27, 2025
e5e0490
chore: add missing variable
huayuenh Feb 27, 2025
97f9c63
fix: stack input reference
huayuenh Feb 27, 2025
4549a64
fix: references
huayuenh Feb 27, 2025
44bfa27
fix: references
huayuenh Feb 27, 2025
c411387
fix: add missing cos crn input
huayuenh Feb 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
159 changes: 76 additions & 83 deletions ibm_catalog.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,20 @@
"description": "Set to `true` to create a Continuous Delivery Service. This is required for running the DevSecOps toolchain pipelines and to successfuly interact with a DevOps Insights integration.",
"required": false
},
{
"key": "project_ci_name",
"required": false,
"type": "string",
"default_value": "CI_Project",
"description": "The name of the IBM Cloud Code Engine CI project."
},
{
"key": "project_cd_name",
"required": false,
"type": "string",
"default_value": "CD_Project",
"description": "The name of the IBM Cloud Code Engine CD project."
},
{
"key": "pipeline_ibmcloud_api_key_secret_name",
"type": "string",
Expand Down Expand Up @@ -292,13 +306,6 @@
"description": "Name of the Git token secret in the secret provider used for accessing the sample (or bring your own) application repository.",
"required": false
},
{
"key": "project_names",
"required": false,
"type": "array",
"default_value": ["CI_Project", "CD_Project"],
"description": "The names of the projects to add the IBM Cloud Code Engine."
},
{
"key": "existing_secrets_manager_crn",
"required": false,
Expand All @@ -307,75 +314,19 @@
"description": "The CRN of an existing Secrets Manager instance"
},
{
"key": "autostart",
"required": false,
"type": "boolean",
"default_value": false,
"description": "Set to `true` to automatically run the CI pipeline."
},
"key": "force_create_standard_api_key",
"type": "boolean",
"default_value": false,
"description": "Set to `true` to force create a standard api key. By default the generated apikey will be a service api key. It is recommended to use a Git Token when using the service api key. In the case where the user has been invited to an account and that user not the account owner, during toolchain creation the default compliance repositories will be created in that user's account and the service api will not have access to those repositories. In this case a Git Token for the repositories is required. See `repo_git_token_secret_name` for more details. The alternative is to set `force_create_standard_api_key` to `true` to create a standard api key.",
"required": false
},
{
"key": "create_git_token",
"required": false,
"type": "boolean",
"default_value": false,
"description": "Set to `true` to create a Git Token secret in the speficied Secrets Manager, using the name set in `repo_git_token_secret_name` and the value set in `repo_git_token_secret_value`."
},
{
"key": "custom_app_repo_title",
"type": "string",
"default_value": "",
"description": "(Optional) The title of the server. e.g. My Git Enterprise Server. Applies to the sample application repository, pipeline config repository and additionally the deployment repository of the CD toolchain. Takes precedence over `repo_title`, if also set.",
"required": false
},
{
"key": "custom_app_repo_root_url",
"type": "string",
"default_value": "",
"description": "(Optional) The Root URL of the server. e.g. https://git.example.com. Applies to the sample application repository, pipeline config repository and additionally the deployment repository of the CD toolchain. Takes precedence over `repo_root_url`, if also set.",
"required": false
},
{
"key": "custom_app_repo_blind_connection",
"type": "string",
"default_value": "false",
"description": "Setting this value to `true` means the server is not addressable on the public internet. IBM Cloud will not be able to validate the connection details you provide. Certain functionality that requires API access to the git server will be disabled. Delivery pipeline will only work using a private worker that has network access to the git server.",
"required": false
},
{
"key": "custom_app_repo_git_id",
"type": "string",
"default_value": "",
"description": "The Git ID for the application repositories. Used by the sample application repository, pipeline config repository and additionally the deployment repository of the CD toolchain. Takes precedence for these repositories over the value set in `repo_git_id`.",
"required": false
},
{
"key": "custom_app_repo_group",
"type": "string",
"default_value": "",
"description": "Specify the Git user or group for your application. This must be set if the repository authentication type is `pat` (personal access token). Used by the sample application repository, pipeline config repository and additionally the deployment repository of the CD toolchain. Takes precedence for these repositories over the value set in `repo_group`.",
"required": false
},
{
"key": "custom_app_repo_git_provider",
"type": "string",
"default_value": "",
"description": "The Git provider type. Used by the sample application repository, pipeline config repository and additionally the deployment repository of the CD toolchain. Takes precedence for these repositories over the value set in `repo_git_provider`.",
"required": false
},
{
"key": "custom_app_repo_git_token_secret_name",
"type": "string",
"default_value": "",
"description": "The name of the Git token secret in the secret provider used for accessing the sample application repository, pipeline config repository and additionally the deployment repository of the CD toolchain. Takes precedence for these repositories over the value set in `repo_git_token_secret_name`.",
"required": false
},
{
"key": "custom_app_repo_git_token_secret_value",
"type": "password",
"default_value": "",
"description": "The personal access token that will be added to the `custom_app_repo_git_token_secret_name` secret in the secrets provider. Note if also using `repo_git_token_secret_name` to set a Git Token in Secrets Manager, the names of the secrets must be different.",
"required": false
},
{
"key": "repo_git_token_secret_name",
"required": false,
Expand All @@ -397,6 +348,13 @@
"default_value": "",
"description": "The name of the Git repository owner/group. This setting applies to all all the compliance repositories and sample app."
},
{
"key": "repo_apply_settings_to_compliance_repos",
"type": "boolean",
"default_value": true,
"description": "Set to `true` to apply the same settings to all the default compliance repositories. Set to `false` to apply these settings to only the sample application, pipeline config and the deployment repositories.",
"required": false
},
{
"key": "repo_git_provider",
"type": "string",
Expand Down Expand Up @@ -542,6 +500,20 @@
"type": "password",
"description": "The private worker service api key that will be added to the `privateworker_credentials_secret_name` secret in the secrets provider.",
"required": false
},
{
"key": "toolchain_access_group_name",
"type": "string",
"default_value": "devsecops-toolchain",
"description": "The name of the DevSecOps access group that is created.",
"required": false
},
{
"key": "use_legacy_ref",
"type": "boolean",
"default_value": true,
"description": "Set to `true` to use the legacy secret reference format for Secrets Manager secrets.",
"required": false
}
],
"outputs": [
Expand Down Expand Up @@ -625,13 +597,6 @@
}
}
},
{
"key": "cluster_name",
"type": "string",
"default_value": "mycluster",
"description": "The name of cluster. Treats the dev and prod cluster as the same cluster.",
"required": true
},
{
"key": "prefix",
"type": "string",
Expand Down Expand Up @@ -674,6 +639,13 @@
"description": "Set to `true` to create a Continuous Delivery Service. This is required for running the DevSecOps toolchain pipelines and to successfuly interact with a DevOps Insights integration.",
"required": false
},
{
"key": "cluster_name",
"type": "string",
"default_value": "mycluster",
"description": "The name of cluster. Treats the dev and prod cluster as the same cluster.",
"required": true
},
{
"key": "ci_cluster_name",
"type": "string",
Expand Down Expand Up @@ -712,7 +684,7 @@
{
"key": "cd_cluster_namespace",
"type": "string",
"default_value": "dev",
"default_value": "prod",
"description": "The name of production cluster namespace.",
"required": false
},
Expand Down Expand Up @@ -865,12 +837,12 @@
"description": "The CRN of an existing Secrets Manager instance"
},
{
"key": "autostart",
"required": false,
"type": "boolean",
"default_value": false,
"description": "Set to `true` to automatically run the CI pipeline."
},
"key": "force_create_standard_api_key",
"type": "boolean",
"default_value": false,
"description": "Set to `true` to force create a standard api key. By default the generated apikey will be a service api key. It is recommended to use a Git Token when using the service api key. In the case where the user has been invited to an account and that user not the account owner, during toolchain creation the default compliance repositories will be created in that user's account and the service api will not have access to those repositories. In this case a Git Token for the repositories is required. See `repo_git_token_secret_name` for more details. The alternative is to set `force_create_standard_api_key` to `true` to create a standard api key.",
"required": false
},
{
"key": "create_git_token",
"required": false,
Expand Down Expand Up @@ -900,6 +872,13 @@
"description": "The name of the Git repository owner/group. This setting applies to all all the compliance repositories and sample app."
},
{
"key": "repo_apply_settings_to_compliance_repos",
"type": "boolean",
"default_value": true,
"description": "Set to `true` to apply the same settings to all the default compliance repositories. Set to `false` to apply these settings to only the sample application, pipeline config and the deployment repositories.",
"required": false
},
{
"key": "repo_git_provider",
"type": "string",
"default_value": "",
Expand Down Expand Up @@ -1044,6 +1023,20 @@
"type": "password",
"description": "The private worker service api key that will be added to the `privateworker_credentials_secret_name` secret in the secrets provider.",
"required": false
},
{
"key": "toolchain_access_group_name",
"type": "string",
"default_value": "devsecops-toolchain",
"description": "The name of the DevSecOps access group that is created.",
"required": false
},
{
"key": "use_legacy_ref",
"type": "boolean",
"default_value": true,
"description": "Set to `true` to use the legacy secret reference format for Secrets Manager secrets.",
"required": false
}
],
"outputs": [
Expand Down
Loading