You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: All
Ruby: All
Distribution: All
Module version: Current master (probably olders as well)
How to reproduce (e.g Puppet code you use)
Run puppet apply -e "aptly::repo { 'testing': }" in /root.
What are you seeing
Puppet tries to recreate the Aptly repository on each run. This is done because aptly -raw=true repo list tries to auto detect the configuration file and this breaks due to insufficient read privileges to /root/.aptly.conf.
This is needed because otherwise the aptly command might run into
permission issue with the currenty $PWD. See tubemogul#62 for more information.
Fixestubemogul#62.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Run
puppet apply -e "aptly::repo { 'testing': }"
in/root
.What are you seeing
Puppet tries to recreate the Aptly repository on each run. This is done because
aptly -raw=true repo list
tries to auto detect the configuration file and this breaks due to insufficient read privileges to/root/.aptly.conf
.https://github.com/aptly-dev/aptly/blob/a64807efdaf5e380bfa878c71bc88eae10d62be1/context/context.go#L92
The reason for is because Puppet switches the UID/GID for this command to 450 (aptly) which obviously has no permission to read
/root
.What behaviour did you expect instead
Works as expected.
Output log
Any additional information you'd like to impart
I see two options to fix this:
/home/aptly
-config $config_filepath
The text was updated successfully, but these errors were encountered: