Open
Description
Proposal
Event Types
- keda.authentication.triggerauthentication.created.v1
- keda.authentication.triggerauthentication.updated.v1
- keda.authentication.triggerauthentication.removed.v1
- keda.authentication.clustertriggerauthentication.created.v1
- keda.authentication.clustertriggerauthentication.updated.v1
- keda.authentication.clustertriggerauthentication.removed.v1
Events scoped to the cluster should not have the “namespace” segment in the subject.
Payload:
{
"specversion" : "1.0",
"type" : "keda.authentication.triggerauthentication.created.v1",
"subject" : "/{kubernetes-cluster-name}/{namespace, only if it’s namespaces}/{cluster-trigger-authentication or trigger-authentication}/{resource-name}/",
"time" : "2018-04-05T17:31:00Z",
"datacontenttype" : "application/json",
"data" : {
"podIdentity": {
"provider": "azure"
},
"secretTargetRef": [
{
"parameter": "<parameter-name>",
"name": "<secret-name>",
"key": "<secret-key-name>"
}
],
"environmentVariables": [
{
"parameter": "<parameter-name>",
"name": "<environment-variable-name>",
"containerName": "<container-name>"
}
],
"hashiCorpVault": {
// Omitted, follow current configuration spec
},
"azureKeyVault": {
"vault": {
"vaultUri": "<URL>",
"resourceUrl": "<URL>",
"cloud": {
"type": "AzurePublicCloud"
}
},
"activeDirectory": {
"client": {
"id": "<id>",
"secretKeyRef": {
"name": "<secret-name>"
"key": "<secret-key-name>"
}
}
"endpoint": "<ad-endpoint-url>",
}
}
}
}
Use-Case
Allow end-users to react to changes to their (Cluster)TriggerAuthentication resource.
Anything else?
Relates to #479
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
To Do