Service Group Configuration
In addition to configuration updates, you can upload files to a service group. Keep these small - we recommend 4k or less per file, and keep the count of files to a minimum.
hab file upload command
to submit a file to a service group. Specify a peer in the ring to connect to,
the version number of the file, and the new path to the file itself.
File updates for service groups must be versioned. The version number must be an integer that starts at one and must be incremented with every subsequent update to the same service group.
If the version number is less than or equal to the current version number, the change(s) will not be applied.
The following example shows how to upload a file to the ring:
hab file upload myapp.prod 1 /tmp/yourfile.txt --remote-sup=hab1.mycompany.com
Your output would look something like this:
» Uploading file yourfile.txt to 1 incarnation myapp.prod Ω Creating service file ↑ Applying via peer 188.8.131.52:9632 ★ Uploaded file
The services in the
myapp.prod service group will receive the file, restarting if necessary:
hab-sup(MR): Receiving new version 1 of file secret.txt for myapp.prod ... myapp.prod(SR): Service file updated, yourfile.txt
Note: Habitat will put the uplodaded file in your service’s
Files can be encrypted for the service group they are intended for. To do so,
--user option with the name of your user key, and the
with the organization of the service group. If you have the public key for the
service group, the data will be encrypted for that key, signed with your user key,
and sent to the ring.
It will then be stored encrypted in memory, and decrypted on disk.
Was this page helpful?