[WIP] update suggestions for add features in aws mutlti zone support

.github/CODEOWNERS

@@ -0,0 +1,19 @@
+# docs: https://help.github.com/en/articles/about-code-owners
+
+# This is a comment.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+# *       @global-owner1 @global-owner2
+
+# Order is important; the last matching pattern takes the most
+# precedence.
+
+# The codeowners of this file are the repository admins
+.github/CODEOWNERS @ereslibre @flavio @innobead @jordimassaguerpla @stefsuse
+
+# A file/directory pattern or domain MUST have at least 3 codeowners before
+# it is added to this file.

.github/pull_request_template.md

@@ -0,0 +1,60 @@
+## Why is this PR needed?
+
+Does it fix an issue? addresses a business case?
+
+add a description and link to the issue if one exists.
+
+Fixes #
+
+**Reminder**: Add the "fixes bsc#XXXX" to the title of the commit so that it will
+appear in the changelog.
+
+## What does this PR do?
+
+please include a brief "management" technical overview (details are in the code)
+
+## Anything else a reviewer needs to know?
+
+Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
+
+## Info for QA
+
+This is info for QA so that they can validate this. This is **mandatory** if this PR fixes a bug.
+If this is a new feature, a good description in "What does this PR do" may be enough.
+
+### Related info
+
+Info that can be relevant for QA:
+* link to other PRs that should be merged together
+* link to packages that should be released together
+* upstream issues
+
+### Status **BEFORE** applying the patch
+
+How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
+this issue is not fixed.
+
+### Status **AFTER** applying the patch
+
+How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
+
+## Docs
+
+If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
+At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
+but the documentation needs to be finalized before the PR can be merged. 
+
+# Merge restrictions
+
+(Please do not edit this)
+
+We are in *v4-maintenance phase*, so we will restrict what can be merged to prevent unexpected surprises:
+
+    What can be merged (merge criteria):
+        2 approvals:
+            1 developer: code is fine
+            1 QA: QA is fine
+        there is a PR for updating documentation (or a statement that this is not needed)
+
+<!-- Remember, if this is a work in progress please pre-append [WIP] to the title until you are ready! 
+    If you can, please apply all applicable labels to help reviews out! -->

.gitignore

@@ -17,4 +17,16 @@
 .glide/
 
 # Binary folder
-/bin
+/bin
+
+# RPM files folder
+ci/packaging/suse/obs_files
+
+# ignore coverage result
+/coverage.out
+
+# ignore skuba
+/skuba
+
+# ignore junit files
+ci/infra/testrunner/pr.xml

.golangci.yml

@@ -0,0 +1,82 @@
+linters-settings:
+  govet:
+    check-shadowing: true
+  golint:
+    min-confidence: 0
+  gocyclo:
+    min-complexity: 15
+  maligned:
+    suggest-new: true
+  dupl:
+    threshold: 100
+  goconst:
+    min-len: 2
+    min-occurrences: 2
+  misspell:
+    locale: US
+  lll:
+    line-length: 140
+  goimports:
+    local-prefixes: github.com/golangci/golangci-lint
+  gocritic:
+    enabled-tags:
+      - diagnostic
+      - experimental
+      - opinionated
+      - performance
+      - style
+    disabled-checks:
+      - wrapperFunc
+      - dupImport # https://github.com/go-critic/go-critic/issues/845
+      - ifElseChain
+      - octalLiteral
+  funlen:
+    lines: 100
+    statements: 50
+
+linters:
+  # please, do not use `enable-all`: it's deprecated and will be removed soon.
+  # inverted configuration with `enable-all` and `disable` is not scalable during updates of golangci-lint
+  disable-all: true
+  enable:
+    - bodyclose
+    - deadcode
+    - depguard
+    - dogsled
+    - errcheck
+    - gofmt
+    - goimports
+    - gosimple
+    - ineffassign
+    - misspell
+    - nakedret
+    - staticcheck
+    - structcheck
+    - typecheck
+    - unconvert
+    - varcheck
+    - whitespace
+
+    # TODO: enable these linters
+    # - dupl
+    # - scopelint
+    # - golint
+    # - funlen
+    # - lll
+    # - gosec
+    # - gocritic
+    # - govet
+    # - gochecknoinits
+    # - interfacer
+    # - unparam
+    # - unused
+    # - goconst
+    # - gocyclo
+    # - stylecheck
+
+run:
+  skip-dirs-use-default: true
+  skip-dirs:
+    - docs
+    - bin
+    - ci

.pre-commit-config.yaml

@@ -0,0 +1,45 @@
+# See https://pre-commit.com for more information
+# See https://pre-commit.com/hooks.html for more hooks
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v2.4.0
+    hooks:
+    -   id: trailing-whitespace
+    -   id: end-of-file-fixer
+    -   id: check-symlinks
+    -   id: check-merge-conflict
+    -   id: check-yaml
+    -   id: check-executables-have-shebangs
+-   repo: local
+    hooks:
+    -   id: go-fmt
+        name: go fmt
+        entry: ./scripts/go-fmt.sh
+        files: '\.go$'
+        language: script
+    -   id: go-vet
+        name: go vet
+        entry: ./scripts/go-vet.sh
+        files: '\.go$'
+        language: script
+    -   id: go-imports
+        name: go imports
+        entry: ./scripts/go-imports.sh
+        files: '\.go$'
+        language: script
+-   repo: https://github.com/golangci/golangci-lint
+    rev: v1.27.0
+    hooks:
+    -   id: golangci-lint
+        args: [--verbose, --timeout=3m]
+        files: '\.go$'
+-   repo: https://github.com/pre-commit/mirrors-autopep8
+    rev: v1.4.4
+    hooks:
+    -   id: autopep8
+        files: '\.py$'
+-   repo: https://github.com/antonbabenko/pre-commit-terraform
+    rev: v1.21.0
+    hooks:
+    -   id: terraform_fmt
+        files: '\.tf$'

CONTRIBUTING.md

@@ -0,0 +1,83 @@
+# Contributing to skuba
+
+The following is a set of guidelines for contributing to this project, hosted by [SUSE](https://github.com/suse/skuba).
+If you have a suggestion to these guidelines feel free to propose changes in a pull request.
+
+
+## Pull requests
+
+Contributors:
+* Adhere to the PR template. Fill out as many sections as possible with as much detail as possible.
+* Adhere to the style guide as closely as possible, where a bot cannot do it for you.
+* The PR is ready for review only when the CI is green. Do not ask for people to review your code if the CI is failing.
+* If CI is not passing, or you need to make more improvements than expected, please add the wip label.
+* Once the CI is green, feel free to assign specific reviewers to your PR to signal it is ready.
+* Do NOT merge pull requests.  CI will automatically merge the PR once tests pass and approvals are received.
+
+Maintainers:
+* Devote time to regular code review and make your reviews impactful. Look at the big picture, don't get hung up on style alone.
+* Veto only when there's is something really problematic, otherwise just comment. Otherwise you are forcing a new round of reviews including a new CI run.
+* Add yourself to the [CODEOWNERS](.github/CODEOWNERS) file if you want to be assigned automatically as reviewer in a particular area.
+
+
+## Styleguides
+
+### git commit messages
+
+This list is not comprehensive, meaning if you want to include more detail than required that is fine as long as you meet these guidelines first.
+
+* Title
+  * Always start with an upper-case letter
+  * Do not put a dot (period) at the end
+  * Use imperative verbs
+  * Maximum characters: 50 (excluding the (bsc#123456) part)
+  * Tracking issues from Bugzilla
+    * Add `(bsc#123456)` as part of the title
+
+* Body
+  * Start sentences with upper-case letter and finish with dot (period).
+  * Maximum characters per line is 72
+  * Explain what this commit is doing
+  * Explain why we have to do it
+  * Do not explain how unless the change is sufficiently large and needs further explanation
+    * Tracking issues from Github:
+      * __Do not track references (ID/URLs) to in the commit message__ but on the web-ui (yes you are forced to open your browser)
+
+## Go style
+
+This will be checked automatically by our CI linter bot.
+
+## Releasing
+
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++ If you are releasing a new kubernetes version, or any other container, +
++ make sure the versions.go has been updated accordingly. See as an      +
++ example:                                                               +
++   https://github.com/SUSE/skuba/pull/573                               +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+In order to create a new release, perform the following steps:
+
+* Create a tag:
+  * Tag with `vX.Y.Z`: `git tag -s vX.Y.Z -m "Tag X.Y.Z" <commit>`
+  * Allowed tag format:
+    * `vX.Y.Z-alphaN?`: creates an alpha release (e.g. `v1.0.0-alpha`,
+      `v1.0.0-alpha3`)
+    * `vX.Y.Z-betaN?`: creates a beta release (e.g. `v1.0.0-beta`,
+      `v1.0.0-beta1`)
+    * `vX.Y.Z-rcN?`: creates a release candidate (e.g. `v1.0.0-rc`,
+      `v1.0.0-rc2`)
+    * `vX.Y.Z`: creates a final release
+  * `<commit>` argument can be omitted if you want the tag to point to `HEAD`
+
+* Push the tag: `git push <remote> vX.Y.Z`
+  * Note: `<remote>` should be pointing to the
+    `github.com/SUSE/skuba` repository
+
+* Checkout the tag: `git checkout vX.Y.Z`
+
+* Create the changelog: `make suse-package`
+
+* Add a new release at https://github.com/SUSE/skuba/releases with the contents from the file `ci/packaging/suse/obs_files/skuba.changes.append`
+
+* Use the files in `ci/packaging/suse/obs_files` to update the skuba package