Bug #33671
don't warn about apipie cache when using "rake config"
Pull request:
Fixed in Releases:
Found in Releases:
Description
foreman-rake config … is often used in automation as an API to fetch/set config options. However, this sometimes includes the ugly "API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache." warning, confusing the app trying to fetch the config.
lets hide the warning when in "config" mode too.
Related issues
Associated revisions
Refs #33671 - print apipie warnings on stderr
warnings should go to stderr, so callers can filter them out, without
filtering the normal output
History
#1
Updated by The Foreman Bot 10 months ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/8829 added
#2
Updated by The Foreman Bot 10 months ago
- Pull request https://github.com/theforeman/foreman/pull/8830 added
#3
Updated by Ewoud Kohl van Wijngaarden 10 months ago
Updated by - Is duplicate of Bug #33369: Print warnings subceptible to show up in a console session to stderr added
#4
Updated by The Foreman Bot 10 months ago
- Fixed in Releases 3.1.0 added
#5
Updated by Evgeni Golov 10 months ago
Updated by - Status changed from Ready For Testing to Closed
Applied in changeset foreman|701fff0b9d81b58428ef0d622dbb1aa2f732ca77.
#6
Updated by Amit Upadhye 9 months ago
Updated by - Category set to Rake tasks
Fixes #33671 - hide apipie warning in config
before this patch:
API controllers newer than Apipie cache! Run apipie:cache rake task to regenerate cache.
false
after this patch:
false