X-Git-Url: https://osm.etsi.org/gitweb/?a=blobdiff_plain;f=installers%2Fcharm%2Fkeystone%2Fconfig.yaml;h=dc0953a9b12d4cd0774452c5a17f3df2ddabe481;hb=de440ed8935a4ad8b7acaad9a6356cedada7bf2b;hp=a606d8e5f25c40facfa64e660e1970141cdcbac3;hpb=49379ced23b5e344a773ce77ac9cb59c1864e19b;p=osm%2Fdevops.git

diff --git a/installers/charm/keystone/config.yaml b/installers/charm/keystone/config.yaml
index a606d8e5..dc0953a9 100644
--- a/installers/charm/keystone/config.yaml
+++ b/installers/charm/keystone/config.yaml
@@ -20,6 +20,11 @@ options:
       If there is a reverse proxy in front of Keystone, it may
       need to be configured to handle the requested size.
     default: 5
+  ingress_class:
+    type: string
+    description: |
+      Ingress class name. This is useful for selecting the ingress to be used
+      in case there are multiple ingresses in the underlying k8s clusters.
   ingress_whitelist_source_range:
     type: string
     description: |
@@ -37,6 +42,16 @@ options:
     type: string
     description: Ingress URL
     default: ""
+  image_pull_policy:
+    type: string
+    description: |
+      ImagePullPolicy configuration for the pod.
+      Possible values: always, ifnotpresent, never
+    default: always
+  security_context:
+    description: Enables the security context of the pods
+    type: boolean
+    default: false
   region_id:
     type: string
     description: Region ID to be created when starting the service
@@ -45,6 +60,11 @@ options:
     type: string
     description: Keystone DB Password
     default: admin
+  mysql_uri:
+    type: string
+    description: |
+      Mysql uri with the following format:
+        mysql://<user>:<pass>@<host>:<port>/<database>
   admin_username:
     type: string
     description: Admin username to be created when starting the service
@@ -185,13 +205,13 @@ options:
       user is enabled.
     default: 0
   ldap_user_enabled_default:
-    type: boolean
+    type: string
     description: |
       Most LDAP servers use a boolean or bit in a control field to indicate
       enablement. However, some schemas might use an integer value in an
       attribute. In this situation, set user_enabled_default to the integer
       value that represents a user being enabled.
-    default: true
+    default: "true"
   ldap_user_enabled_invert:
     type: boolean
     description: |