chore: allow optional policy use

Author: huayuenh

ibm_catalog.json

@@ -314,6 +314,13 @@
 							"description": "Set to `true` to automatically run the CI pipeline."
 						},
 						{
+                            "key": "force_create_standard_api_key",
+                            "type": "boolean",
+                            "default_value": true,
+                            "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",
@@ -872,6 +879,13 @@
 							 "description": "Set to `true` to automatically run the CI pipeline."
 						 },
 						 {
+                            "key": "force_create_standard_api_key",
+                            "type": "boolean",
+                            "default_value": true,
+                            "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",

kubernetes/stack_definition.json

@@ -100,6 +100,14 @@
 			"default": "devsecops-rg",
 			"custom_config": {}
 		},
+		{
+			"name": "force_create_standard_api_key",
+			"required": false,
+			"type": "boolean",
+			"hidden": false,
+			"default": true,
+			"custom_config": {}
+		  },
 		{
 			"name": "prefix",
 			"required": false,
@@ -757,6 +765,10 @@
 					"name": "create_icr_namespace",
 					"value": "ref:../../inputs/create_icr_namespace"
 				},
+				{
+					"name": "force_create_standard_api_key",
+					"value": "ref:../../inputs/force_create_standard_api_key"
+				},
 				{
 					"name": "create_git_token",
 					"value": "ref:../../inputs/create_git_token"

stack_definition.json

@@ -191,7 +191,7 @@
       "required": false,
       "type": "boolean",
       "hidden": false,
-      "default": false,
+      "default": true,
       "custom_config": {}
     },
     {