Fixes #37436 - Remove TimedCacheStore class

Foreman uses either redis or file store for quite some time.
This class is not being used anywhere.

Fixes #37161 - load public/webpack when available

Refs #36815 - Require redis group if it is present

Refs #36815 - explicitly require redis

ActiveSupport only loads the Redis gem when one enables RedisCacheStore,
but we need to obtain the default values before that.

For some reason this did not break on EL, but only on Debian.
Maybe because we use plain gems on the one vs bundler on the other....

Fixes #36842 - reduce impact of rails-cache issue

Original rails-issue: https://github.com/rails/rails/issues/49690

Fixes #36815: Set Redis reconnect_attempts to default

Fixes #36583 - Remove power_manager from autoload_paths

This directory no longer exists.

Fixes: 3484613f7fb7 ("fixes #2411 - move files in /models to /concerns, /services, /mailers, /observers")

Fixes #35432 - Use Rails 6.1 defaults

Refs #36330 - Place assets into plugin dir

Fixes #36331 - Expose translation registration in plugin DSL

Fixes #35088 - Remove GCE Compute resource code

All code related to GCE compute resource
is now in Foreman Google plugin

https://github.com/theforeman/foreman_google

Fixes #35210 - Allow symbols and hashes in YAML columns

Fixes #34994 - require ApplicationRecord early for migrations

Without this migrations that use models fail with

PG::UndefinedTable: ERROR:  relation "application_records" does not exist

Fixes #34646 - move initialization into initializer (#9155)

Tidies up application.rb by moving initialization steps into initializer.
This also makes sure that Facets are not the first subclass inheriting from ApplicationRecord.
Facets being first derails Rails initialization.

Fixes #34526 - rescue_from JSON params parse errors

Use rescue_from block instead of the CatchJsonParseErrors middleware
See https://github.com/rails/rails/pull/34341

Fixes #34391 - use facets to expose reported data in API

We use only uptime_seconds in the API and not even properly.
Facets should have its own view to separate its data from the main host attributes.

Refs #10413 - Drop unattended mode check in app init

Fixes #30122 - remove usage of controller level force_ssl

Foreman's use case for HTTP-only is provisioning. Many installers, like Red
Hat's Anaconda or Debian Preseed, either do not support it or make it very hard
to use HTTPS. This is especially hard since often a custom CA is used so the...

Fixes #34353 - Fix early load of fog_extensions

Fixes #34366 - skip GraphQL types enhancements in migrations

GraphQL types try to touch database, but that is not possible during the db migration.
These fields enhancements needs to be disabled during migrations.

Fixes #34165 - Require code from lib folder

Fixes #33967 - Loading constants in initializers/active_record_extensions.rb

Fixes #32328 - Infrastructure roles

Introduces things needed to assign infrastructure roles to hosts.

A host can now have an infrastructure facet, which can be used to mark a
host as foreman instance by setting a flag on the facet. The facet can
also be used to establish a relationship between the host and a smart...

Fixes #14854 - connection libvirt leak fixed

Fixes #33008 - switch to sql schema dumping

Fixes #33013 - Silence bundler in production

In production deployments the Rails directory is usually not writable.
This leads to warnings. By using the silent UI this is hidden from
users.

Fixes #32635 - fix already initialized constant

Fixes #29782: Drop Passenger work arounds

Fixes #30779 - Implement ActionDispatch::RemoteIp (#7960)

The ActionDispatch::RemoteIp middleware can provide the remote IP
correctly as a property of the request object. This looks at
X-Forwarded-For headers while stripping out reverse proxies and falls...

Fixes #31669 - Register RegistrationFacet in application.rb

Refs #30667 - Use separate logger config for sidekiq workers

Sidekiq emits two log messages for each job it processes and those end up in
system journal and possibly /var/log/messages. Originally I opened a PR so
sidekiq workers would "inherit" their log levels from Dynflow loggers. This made...

Fixes #30126 - use facets fact parsing

Refs #30098 - Drop trends models

Fixes #30030 - use media_type where appropriate

Also, set config.action_dispatch.return_only_media_type_on_content_type
to false, as it will be in Rails 6.1.

Refs #29872 - Always require test_unit railtie

It is required for defining the 'test' rake tasks.

Fixes #29872 - Only load used Rails frameworks

Fixes #29284 - Drop Rackspace support

Fixes #29642 - drop sqlite support

Fixes #19892 - Fix Style/Proc cop

Fixes #29311 - Add Rails logging for API deprecation warnings.

Fixes #29258 - Initialize dynflow in puma workers

When running puma in clustered mode in production, Dynflow would get initialized
in the master process before workers were forked off and due to CoW the workers
would use the same world id.

With this commit we will eagerly initialize Dynflow only when running under...

Fixes #19792 - Fix Layout/SpaceInsideBlockBraces cop

Fixes #28576 - Fix Style/RedundantBegin cop

Fixes #28511 - Fix Lint/SendWithMixinArgument cop

Fixes #24838 - Use integer representation for boolean on sqlite

We don't really need to migrate boolean fields as sqlite isn't supported
production database and is only used for running build tasks.

Fixes #26393 - extract uptime to reported facet

A new Reported Data facet is introduced. This should be used for storing
reported information from various fact parsers. Fact Parser now defines
a new optional to implement method, to gather boot time in seconds. Some...

Fixes #26681 - new logger named taxonomy

fixes #26541 - graphql: add plugin api

refs #26918 - adds redis support in docker-compose

this uses environment variables support introduced in 47aca03d3f3be870aab808b58480f281863de766
and also fixes a minor typo.

[skips ci]

fixes #26918 - add a redis caching backend

Fixes #26039 - disable blob logger by default

fixes #26002 - set cors header via env variable

Fixes #25829 - Remove notification for removed settings

The deprecated settings have been removed, so these notifications will
never be displayed anymore. Keeping the blueprint in place so we can
reuse it in the future if needed.

Fixes #25619 - refactor logging middleware

Fixes #25492 - Remove the :login setting

Fixes #24800 - Notify deprecation of taxonomy, login settings

Fixes #24710 - extend audits in to_prepare

Fixes #24539 - don't initialize dynflow in db:create

It fails on Rails 5.2

Fixes #23579 - Use a bundler group for assets

Fixes #23962 - Fix Style/ExpandPathArguments cop

Fixes #23142,#23503 - telemetry improvements

Fixes #19781 - Fix Layout/LeadingCommentSpace cop

Fixes #23223 - Don't allow Dynflow to initialize in db:drop rake

Fixes #23098 - Allow searching on all audited models by type (#5395)

This automatically adds all the audited models in an after_initilize
block so that models defined in plugins are also included. All the
search related definitions for audit have been extracted to a seperate...

Refs #22285 - Prepare tests for strong params enforcement

- Fix broken hosts api tests
- Fix role cloning tests
- Fix ssh key controller api test
- Fix http proxies controller test
- Fix lookup key override api controller test
- Fix puppetclass controller api test...

Refs #22285 - add common parameters to strong_params whitelist

Despite the name, this list only prevents errors from being raised from
these parameters which are still filtered.

Fixes #19793 - Fix Layout/SpaceInsideReferenceBrackets cop

Fixes #22888 - remove code around dynflow db_pool_size

Remove the code in favor of the Dynfow, where we can handle all the
logic at one place.

Fixes #22493 - structured logging support

Refs #18675 - Optionally load prometheus exporter

In case the bundler group telemetry is not installed, we should handle
that.

This moves the middleware loading to better match the other middleware.

Fixes #21097 - Update to Rails 5 configuration options

Fixes #21084 - Always Use Rails 5.0, Drop Rails 4.2

Fixes #18292 - Make notifications from an RSS feed (#4240)

This adds a task to connect to an RSS feed, by default the one from our
community blog. The idea is to make this run every night with 'cron' on
every Foreman installation to keep people updated about changes, and...

Fixes #21295 - load the routes before we load the controllers

After upgrade from Rails 4.1 to Rails 4.2 there was significant
drop on rails startup in production. I have tracked it down to
several changes in Rails, but it might also be affected by the
fact the we use the url_helpers on more places than older Foreman...

Fixes #20201 - Global HTTP proxy for outgoing requests

This introduce two new settings to proxy outgoing HTTP
requests and one to except certain hosts from it.

The extensions for Excon::Connection and Net::HTTP
allow setting a proxy on their requests.

Fixes #20908 - postpone initialization of Dynflow runtime

In #18618, the initialization code was moved from foreman-tasks to
foreman. There was however one thing done differently, where the
initialization of dynflow world was moved directly to the time
`Rails.application.dynflow` was called. This is not right, as there are...

fixes #10982 - configure RestClient log to 'proxy' logger

Request/response information is sent to the proxy logger, showing the
URLs called, headers, request body etc.

The X-Request-ID header is now also set in the proxy requests to a
random ID stored in the session, to prevent the user's real session ID...

Fixes #18618 - Use Dynflow as an ActiveJob backend

This commit initializes the Dynflow world in a very similar manner to
foreman-tasks (if a Dynflow world is available from foreman-tasks, we
use that one).

fixes #18500 - replace quiet_assets with sprockets-rails flag

• fixes #18512 - support sprockets-rails 3.x

The app.assets environment is no longer always configured, and instead
is only configured when the regular Rails environment is loaded. Loading
only the 'assets' group initializers isn't sufficient....

fixes #19050 - add Ruby on Rails 5.0 support

Adds configurable support for running on Ruby on Rails 5.0 or 4.2,
defaulting now to 5.0 on Ruby 2.3 or higher. Ruby versions with partial
or no support remain using 4.2 by default. Other points:

1. SETTINGS[:rails] is loaded pre-Rails boot, then post-boot the...

Fixes #19728 - set admin user in rake console

fixes #19317, #10927 - move registries to autoload_once path

Partially reverts 70ce8fe to reinstate autoload_once_paths as the
preferred way to load registry-type objects with class variables
containing data set up during app initialisation (e.g. plugin
registrations, menu items.)...

Refs #13772 - ensure ApplicationRecord is loaded soon enough

In `lib/core_extensions.rb` we define as `per_page` method, that gets
called by `will_paginate` at load time of the models. The issue is
we are using `Setting` model there, that inherits from the...

fixes #18445 - always define eager_load_paths, use require_dep

Allows `eager_load!` to be called or enabled in any environment without
loading files under lib/ twice. Switches many `require` calls to Rails'
`require_dependency` to always use its dependency loader, so when eager...

fixes #18681 - moves polymorphic subject into notification object

also adds host build, destroyed and missing owner UI notifications

Refs #15779 - make background processing unavailable for now (#4217)

The original PR got vetted in the packaging phase and including
foreman-task as dependency of Foreman was refused. We need to rethink
our approach for getting the foreman-tasks functionality available...

Refs #15779 - move the foreman-tasks to own bundle group

This makes it easier to achieve a minimal setup, that might be needed for
things like plugins building etc.

Fixes #17343 - set deep munge config off

deep_munge was introduced as a solution to keep
Rails secure by default which results in
'empty array becomes nil in params'.
Thats why, set deep_munge config off in application.rb.
Also, added changes which will cast param argument to string...

Fixes #16643 - Display origin for facts

This commit sets the interfaces for the fact importers to start setting
a Fact origin, and display it in the UI

Fixes #9016 - improved fact loading performance

This change improves fact loading performance by order of magnitude on
SQLite mostly thanks to explicit transaction. An extra optimization was
done for the most important "update" method call which is mostly used...

fixes #16567 - use constants to register Rack middleware

Fixes #12634 - New HW Model flag pxe_loader

Implementation of

https://github.com/theforeman/rfcs/blob/master/text/0001-PXE-Booting-UEFI.md

In short, new host/hostgroup flag PXE loader is added to specify TFTP
DHCP filename and Foreman now orchestrates all PXE-capable templates...

fixes #15863 - add short session or request ID to logs

New middleware stores the session and request IDs (either from
X-Request-ID or a UUID generated by Rails) in the logger's thread
storage. The truncated session ID is now logged by default to minimise...

fixes #14913 - configure Hirb/Wirb via irbrc

Wirb 2.x can't be started before the IRB session itself, so use an irbrc
file per its docs to activate it and Hirb when starting a console.

Refs #3809 - Turning on some rubocop cops

fixes #14912 - setup console gems under bundler_ext

fixes #14820 - override Rails log level with Foreman::Logging config

The log_level is expected to be explicitly configured in the Rails
config in the production environment.

fixes #13244 - update Rails to 4.2.6

- Add responders gem to support class-level respond_to usage
- http://edgeguides.rubyonrails.org/4_2_release_notes.html#respond-with-class-level-respond-to
- Replace foreigner with native Rails 4.2 FK support
- uses a patch from Rails 5 to support Foreigner's...

Fixes #14588 - introduce plugin API for extending template helpers

fixes #14415 - check CR availability with Fog, not SETTINGS

Simplifies the code for checking compute resource availability, which
can easily be determined with the registered Fog providers instead of
being stored in SETTINGS in app initialisation. Plugins should always be...