Secret stored in the vault as a dictionary get_secret_metadata ( self, secret_path ) В¶ Secret_path ( str) - Path of the secret Return type Secret_version ( Optional ) - Optional version of key to read - can only be used in case of version 2 of KV get_secret ( self, secret_path, secret_version = None ) В¶ Radius_port ( Optional ) - Port for radius (for radius auth_type)Д¬onn_name_attr = vault_conn_id В¶ default_conn_name = vault_default В¶ conn_type = vault В¶ hook_name = Hashicorp Vault В¶ get_conn ( self ) В¶ Radius_host ( Optional ) - Host for radius (for radius auth_type) Gcp_scopes ( Optional ) - Comma-separated string containing OAuth2 scopes (for gcp auth_type)ДЄzure_tenant_id ( Optional ) - The tenant id for the Azure Active Directory (for azure auth_type)ДЄzure_resource ( Optional ) - The configured URL for the application registered in Azure Active Directory Gcp_key_path ( Optional ) - Path to Google Cloud Service Account key file (JSON) (for gcp auth_type) Token_path ( Optional ) - path to file containing authentication token to include in requests sent to Vault var/run/secrets/kubernetes.io/serviceaccount/token) Kubernetes_jwt_path ( Optional ) - Path for kubernetes jwt token (for kubernetes auth_type, default: Kubernetes_role ( Optional ) - Role for Authentication (for kubernetes auth_type)

Role_id ( Optional ) - Role ID for aws_iam Authentication. Version defined in connection or 2 if not defined in connection. Kv_engine_version ( Optional ) - Select the version of the engine to run ( 1 or 2). ('approle', 'github', 'gcp', 'kubernetes', 'ldap', 'token', 'userpass')ДЄuth_mount_point ( Optional ) - It can be used to define mount_point for authentication chosenДefault depends on the authentication method used. Vault_conn_id ( str) - The id of the connection to useДЄuth_type ( Optional ) - Authentication Type for the Vault. Userpass: login -> username, password -> password Ldap: login -> username, password -> password 'vaults' and 'https' (using https to connect to the vault).ДЄpprole: login -> role_id, password -> secret_idДЄws_iam: login -> key_id, password -> secret_idДЄzure: login -> client_id, password -> client_secret The URL schemas supported are 'vault', 'http' (using http to connect to the vault) or You can also use gcp_keyfile_dict extra to pass json-formatted dict in case of 'gcp' authentication. The extras in the connection are named the same as the parameters ('kv_engine_version', 'auth_type'. Each engine uses it's own engine-specific authentication mount_point. Note that this mount_point is not used for authentication if authentication is done via aДifferent engines. This indicates the 'path' the secret engine is mounted on. The mount point should be placed as a path in the URL - similarly to Vault's URL schema: Via init params or via corresponding extras in the connection. The login/password from the connectionДЄre used as credentials usually and you can specify different authentication parameters You connect to the host specified as host in the connection. Hook to Interact with HashiCorp Vault KeyValue Secret engine. VaultHook ( vault_conn_id = default_conn_name, auth_type = None, auth_mount_point = None, kv_engine_version = None, role_id = None, kubernetes_role = None, kubernetes_jwt_path = None, token_path = None, gcp_key_path = None, gcp_scopes = None, azure_tenant_id = None, azure_resource = None, radius_host = None, radius_port = None ) В¶

Hook to Interact with HashiCorp Vault KeyValue Secret engine.Д¬lass .vault.

Apache with local password vault