A Generic Integration is an integration type that is not for linking to a specific service, but exists exclusively to securely store key-value pairs of information. This is appropriate for storing secrets such as tokens or passwords for retrieval by a step.
When you add this integration to a step, all key-value pairs are made available as environment variables in the form:
int_<integration-name>_<key>
For example, a Pipelines admin can define a Generic integration with the following entries:
Name:
myCredentialsCustom Environment Variables:
Key:
usernameValue:
janedoeKey:
passwordValue:
nAm30fMyp3t
When myCredentials is specified in a step's integrations block, the key-value pairs stored there can then accessed in the step as environment variables:
pipelines:
- name: generic_integration_example
steps:
- name: step_1
type: Bash
configuration:
integrations:
- name: myCredentials
execution:
onExecute:
- printenv int_myCredentials_username
- printenv int_myCredentials_password