Using Data Job Properties vs Secrets

Properties vs Secrets

This article outlines when and how you should use Data Job Properties or Secrets. While both mechanisms can be used somewhat interchangeably there are certain things you should be aware of:

• Properties are used to store state and non-sensitive data and are generally faster to access and modify. If you need to overwrite a value often, sometimes on multiple occasions during the execution of a data job - properties are the way to go. They are stored in plain text in the VDK Control Service Data Base.
• Secrets are generally fast to access (somewhat slower than Properties), but slow to modify, as they are encrypted/decrypted during the storage/retrieval process. They are best suited for storing sensitive data - secrets, passwords, credentials, tokens, API keys, etc. They are stored in an encrypted stated in a Secure Storage - for example a Hashicorp Vault instance.

Properties Example

Secrets Example

Conclusion