![]() ![]() This key allows the pillar data to be transmitted to the target system during a state or orchestration file program. When pillar data is assigned to a specific target system and included in state files, it is processed by the master for each minion system and encrypted with a separate AES key for each minion. Salt module index for a list of all modulesĪfter defining your pillar data, you can assign the pillar data to a group of minion systems by clicking Update Targets, selecting the target group, and then clicking Save.The following table lists some helpful resources for more information: To learn about. Before you startīecause SaltStack Config is powered by Salt, it helps to have a basic working knowledge of Salt and the concepts related to these features. The syntax you choose to use will depend on your needs and the type of data you need to store. ![]() This example shows three different methods for formatting your pillar data. A typical pillar file might look like this: pillar1: value Pillar data is stored as a dictionary and uses key-value pairs to look up values. Pillar files are usually written in YAML and Jinga, but other formats such as JSON are compatible with Salt. This key is also used to decrypt the data for display in the SaltStack Config UI. Once the Pillar data is defined in the SaltStack Config UI, it is encrypted with this key and stored in the PostgreSQL database. Then, you could write a state file that tells the minion to look up their unique password in the file without having to create multiple files or store passwords in multiple places.ĭata stored in the SaltStack Config Pillar Store is encrypted using the Raas encryption key associated with the specific instance of SaltStack Config (for example: “/etc/raas/pki/.raas.key”). For example, you could assign different passwords to different minions and store all the passwords in one pillar file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |