Disable apt-key usage when salt version is at least 3005, and the user
provides 'signed-by=' in their source, and we're on a newer version of
Debian or Ubuntu.
apt-key is deprecated, see the following for more context:

https://docs.saltproject.io/en/latest/ref/states/all/salt.states.pkgrepo.html#apt-key-deprecated

Signed-off-by: M. David Bennett <mdavidbennett@syntheticworks.com>

The new syntax has been supported since ~2017.
From the docs, in case they change:

! New Style
test.random_hash:
  module.run:
    - test.random_hash:
      - size: 42
      - hash_type: sha256

! Legacy Style
test.random_hash:
  module.run:
    - size: 42
    - hash_type: sha256

See salt issues #48309 #51925

* Ubuntu pinning params allow to be used
     multiply times. In same time, old `list`
     format now allowing to be predictable
     iterated inside jinja

Related-Bug: PROD-21604 (PROD:21604)

Change-Id: If1c0f0f834a296b9a19d0af5fc7673c9229a7ac5

* Add\fix __virtual__ for modules
  * Remove unneded multiline for repo.sls

Change-Id: I1f8d321b68dfe6a44264b4ddcd6cd0c576938da1

Change-Id: I511996de9d8abc69d6775b45482f8196c7159a1a

* Fix processing disabled repo
   * Extend tests for such case

Change-Id: Ib3243f2b3e70aecef65273be215b30613b8df025
Closes-Bug: PROD-21954 (PROD:21954)

Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>

- Add possibility to remove prereq. packages installation BEFORE
     * Crucial logic violation - if we don't have any repo\
       have them configured in wrong way - stage will always fail.
     * install prereq. packages after all - sounds stupid, but correct.
     * By default - it will still try to install prereq. We don't want to
       broke OLD logic.See readme, how-to overide such behaviour.
   - don't update cache per-repo - it's simply useless and may fail due p1.
     Run update only once - after all repos configured\reconfigured
   - Add new option at system:refresh_repos_meta - for case, when update
     should not be run in any case. By default - true.
   - remove 99proxies-salt-{{ name }} along with disabled repo
   - fix duplicate 'clean_file' option

Closes-Bug: PROD-15992 (PROD:15992)

Change-Id: I4b312f82f65be80e7726f62482978f68c25746a3

* Make system.repo more readable

Change-Id: I0f28e71f4b00422a70006559525e5be24c4cb065

- fixed pkgrepo.manage to use/prefer key_url for salt >= 2017.7
- updated syntax for key verificatoin
- fix, avoid curl for salt:// schema (as in #156)

Change-Id: I1b50c287a4030a9cefa1b819017d59cc5fb1c197

Commit totally broke all deployment CI job.

This reverts commit 24477c590b.

Change-Id: Idce0954f0bd363095069e91edc6941ca78b22c60

Change-Id: Id5b5a44f3dfbbdd60442fd2f273b72557fa9e191

Change-Id: I2d374a589e18f38f91beac9514ff5bf3c034d637

* Currently, 'key' was processed only for default repos
  * Remove double-definition
  * Re-use idempotent fix

Co-Authored-By: Dennis Dmitriev <ddmitriev@mirantis.com>

Change-Id: Ic733f671b39e7b4a8d8e0a83515b6b0632c3a41b

Add check for existing key for idempotency.

iteritems() was dropped in recent Python3 releases and items() is compatible
with Python 2.7.

The patches fixes the situation when repo is not defined but
formula tries to get access to source parameter of the repo.

Change-Id: Ifa7b8475bfc2cece6803ab7da7b2d0d5cc12b652
Related-PROD: PROD-17001

Change-Id: I811cbb17d98df357c4b44bd53ddcc5d01a06537f

Change-Id: Id9d9178ca7417df1b8a83110e92cf4a62907982d

Change-Id: Ib7f34360b7580cbc4260b826d1eb21d443801fa5

Change-Id: I7919ef2273185081d56a40af1e8fb4e602da41a2

Closes-Bug: #PROD-10623
Change-Id: I9e070f7f96b1f0b8eafa12403c5df4ae5be3e42c

- allow multiple repos configured on one system (nightly/testing/stable)

Change-Id: I4fd6cafb72fb1ad89c6595782d6705f49777761b

Change-Id: Ifaa3adff756ed63f8e1f66d5de344cb0ab1c9e94