Albarkar exec ta Puppet tana da sifa environment. Sanya ƙimar wakili a kan albarkar da ke kiran mai zazzagewa:

file { '/var/cache/myapp':
  ensure => directory,
}

exec { 'fetch-artifact':
  provider    => shell,
  command     => '/usr/bin/wget --tries=1 --timeout=20 -O /var/cache/myapp/artifact.part https://downloads.example.net/artifact-v1.bin && /usr/bin/mv /var/cache/myapp/artifact.part /var/cache/myapp/artifact-v1.bin',
  environment => [
    'http_proxy=http://proxy.example.net:8080',
    'https_proxy=http://proxy.example.net:8080',
  ],
  creates     => '/var/cache/myapp/artifact-v1.bin',
  require     => File['/var/cache/myapp'],
}

Misalin yana ɗauka cewa Wget da mv suna kan waɗannan hanyoyin. Matsayin da bai yi nasara ba yana barin sunan hanyar wucin gadi; ana girka sunan hanyar ƙarshe ne kawai bayan Wget ya yi nasara. Bayan haka tsaron creates yana tsallake tafiyar da za a yi daga baya muddin fayil ɗin da aka kammala mai sigar yana nan.

Tsarin yanayi yana ba da ƙima lokacin da Puppet ke tafiyar da wannan umarni. Shigar HTTP daga jerin wakilan HTTP na iya ba da URL ɗin wakili don zazzagewar kayan aikin jama'a da aka yarda da shi lokacin da Wget ba shi da tabbacin wakili da aka saita ko aka riƙe. Fitar da wani albarkar exec ya yi yana aiki ne kawai a cikin wancan tsari da zuriyarsa. Yin odar albarkatu biyu ba ya sa yanayin harsashi na farkon ya dawwama a na biyu.

Riƙe yanayin wannan albarkar tare da albarkar. Sauran ayyukan Puppet na iya amfani da hanyoyinsu da aka saita ba tare da canza fayil ɗin fara Wget na dukan na'urar ba.

Labarai masu alaƙa