[BACKPORT][1.0.1] Allow to specify configuration to be used in upgrade mode

[seriva]

Source issue #2127
Pull request #2384

---

DoD checklist

• Changelog updated
• COMPONENTS.md updated / doesn't need to be updated
• Feature has automated tests
• Automated tests passed (QA pipelines)
  • apply
  • upgrade
• Idempotency tested
• Documentation added / updated / doesn't need to be updated
• All conversations in PR resolved
• Solution meets requirements and is done according to design doc
• Usage compliant with license
• Backport tasks created / doesn't need to be backported

[przemyslavic]

The following scenario was tested:

• epicli apply v.0.9.2
• cat ../build/$(cluster_name)/ansible/roles/logging/vars/main.yml

2021-07-09T08:46:40.9864342Z kind: configuration/logging
2021-07-09T08:46:40.9865087Z title: Logging Config
2021-07-09T08:46:40.9865498Z name: default
2021-07-09T08:46:40.9865829Z specification:
2021-07-09T08:46:40.9866183Z   cluster_name: EpiphanyElastic
2021-07-09T08:46:40.9866530Z   clustered: true
2021-07-09T08:46:40.9866853Z   paths:
2021-07-09T08:46:40.9867197Z     data: /var/lib/elasticsearch
2021-07-09T08:46:40.9868029Z     repo: /var/lib/elasticsearch-snapshots
2021-07-09T08:46:40.9868461Z     logs: /var/log/elasticsearch
2021-07-09T08:46:40.9869220Z   jvm_options:
2021-07-09T08:46:40.9869551Z     Xmx: 1g
2021-07-09T08:46:40.9869874Z   provider: aws
2021-07-09T08:46:40.9870199Z version: 0.9.2

• cat ../build/$(cluster_name)/ansible/roles/rabbitmq/vars/main.yml

2021-07-09T08:46:40.9871018Z kind: configuration/rabbitmq
2021-07-09T08:46:40.9871567Z title: RabbitMQ
2021-07-09T08:46:40.9872387Z name: default
2021-07-09T08:46:40.9875378Z specification:
2021-07-09T08:46:40.9876446Z   rabbitmq_user: rabbitmq
2021-07-09T08:46:40.9876834Z   rabbitmq_group: rabbitmq
2021-07-09T08:46:40.9877182Z   stop_service: false
2021-07-09T08:46:40.9877543Z   logrotate_period: weekly
2021-07-09T08:46:40.9877934Z   logrotate_number: 10
2021-07-09T08:46:40.9878297Z   ulimit_open_files: 65535
2021-07-09T08:46:40.9878636Z   amqp_port: 5672
2021-07-09T08:46:40.9879011Z   rabbitmq_use_longname: AUTOCONFIGURED
2021-07-09T08:46:40.9879401Z   rabbitmq_policies: []
2021-07-09T08:46:40.9879755Z   rabbitmq_plugins:
2021-07-09T08:46:40.9880451Z   - rabbitmq_management_agent
2021-07-09T08:46:40.9881027Z   - rabbitmq_management
2021-07-09T08:46:40.9881428Z   custom_configurations: []
2021-07-09T08:46:40.9881893Z   cluster:
2021-07-09T08:46:40.9882597Z     is_clustered: true
2021-07-09T08:46:40.9882930Z   provider: aws
2021-07-09T08:46:40.9883456Z version: 0.9.2
2021-07-09T08:46:40.9884087Z provider: aws

• create configuration file for upgrade

---
kind: configuration/rabbitmq
title: "RabbitMQ"
provider: aws
name: default
specification:
  logrotate_period: daily
  logrotate_number: 9
  ulimit_open_files: 256
  rabbitmq_plugins:
    - rabbitmq_management_agent
    - rabbitmq_management
  cluster:
    is_clustered: false
---
kind: configuration/logging
title: Logging Config
name: default
provider: aws
specification:
  cluster_name: NameAferUpgrade
  jvm_options:
    Xmx: 2g

• execute epicli upgrade with -f /shared/$(cluster_name)/$(cluster_name)_upgradeconfig.ym parameter
• cat ../build/$(cluster_name)/ansible/roles/logging/vars/main.yml

2021-07-09T09:40:30.1184880Z kind: configuration/logging
2021-07-09T09:40:30.1186333Z title: Logging Config
2021-07-09T09:40:30.1186857Z specification:
2021-07-09T09:40:30.1187205Z   cluster_name: NameAferUpgrade
2021-07-09T09:40:30.1187878Z   clustered: true
2021-07-09T09:40:30.1188239Z   admin_password: PASSWORD_TO_CHANGE
2021-07-09T09:40:30.1188632Z   kibanaserver_password: PASSWORD_TO_CHANGE
2021-07-09T09:40:30.1189036Z   kibanaserver_user_active: true
2021-07-09T09:40:30.1189431Z   logstash_password: PASSWORD_TO_CHANGE
2021-07-09T09:40:30.1189819Z   logstash_user_active: true
2021-07-09T09:40:30.1190178Z   demo_users_to_remove:
2021-07-09T09:40:30.1190843Z   - kibanaro
2021-07-09T09:40:30.1191323Z   - readall
2021-07-09T09:40:30.1191788Z   - snapshotrestore
2021-07-09T09:40:30.1192096Z   paths:
2021-07-09T09:40:30.1192406Z     data: /var/lib/elasticsearch
2021-07-09T09:40:30.1192980Z     repo: /var/lib/elasticsearch-snapshots
2021-07-09T09:40:30.1193376Z     logs: /var/log/elasticsearch
2021-07-09T09:40:30.1193715Z   jvm_options:
2021-07-09T09:40:30.1194016Z     Xmx: 2g
2021-07-09T09:40:30.1194319Z   opendistro_security:
2021-07-09T09:40:30.1194644Z     ssl:
2021-07-09T09:40:30.1194941Z       transport:
2021-07-09T09:40:30.1195319Z         enforce_hostname_verification: true
2021-07-09T09:40:30.1195693Z   provider: aws
2021-07-09T09:40:30.1195984Z version: 1.0.0
2021-07-09T09:40:30.1196337Z provider: aws

• cat ../build/$(cluster_name)/ansible/roles/rabbitmq/vars/main.yml

2021-07-09T09:40:30.1196659Z kind: configuration/rabbitmq
2021-07-09T09:40:30.1196986Z title: RabbitMQ
2021-07-09T09:40:30.1197291Z specification:
2021-07-09T09:40:30.1197603Z   rabbitmq_user: rabbitmq
2021-07-09T09:40:30.1197951Z   rabbitmq_group: rabbitmq
2021-07-09T09:40:30.1198294Z   stop_service: false
2021-07-09T09:40:30.1198636Z   logrotate_period: daily
2021-07-09T09:40:30.1198979Z   logrotate_number: 9
2021-07-09T09:40:30.1199307Z   ulimit_open_files: 256
2021-07-09T09:40:30.1199638Z   amqp_port: 5672
2021-07-09T09:40:30.1199998Z   rabbitmq_use_longname: AUTOCONFIGURED
2021-07-09T09:40:30.1200374Z   rabbitmq_policies: []
2021-07-09T09:40:30.1200708Z   rabbitmq_plugins:
2021-07-09T09:40:30.1201245Z   - rabbitmq_management_agent
2021-07-09T09:40:30.1201769Z   - rabbitmq_management
2021-07-09T09:40:30.1202120Z   custom_configurations: []
2021-07-09T09:40:30.1202456Z   cluster:
2021-07-09T09:40:30.1202756Z     is_clustered: false
2021-07-09T09:40:30.1203086Z   provider: aws
2021-07-09T09:40:30.1203390Z version: 1.0.0
2021-07-09T09:40:30.1203689Z provider: aws

The functionality seems to be working fine. However, to take full advantage of it, we should adjust all upgrade playbooks in the future.