Initial commit

Signed-off-by: Marc Lopez <[email protected]>

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# These owners will be the default owners for everything in
+# the repository.
+*       @elastic/cloud-tooling

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,22 @@
+<!--- Thank you for taking the time to create an issue! -->
+
+<!--- Before creating a new issue, please consider whether -->
+<!--- you could open a more specific issues such as a -->
+<!--- dedicated Bug Report, Feature Request, or alternatively -->
+<!--- raise a Generic Question.  Opening a generic issue, -->
+<!--- whilst not incorrect is generally discouraged. -->
+
+<!--- Provide a general summary of the issue in the title above. -->
+
+## Description
+<!--- Describe your issue using as much detail as possible, but -->
+<!--- please keep your question clear and concise. -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment -->
+<!--- you experienced the bug in. -->
+* Version used:
+* Environment name and version (e.g. Go 1.9):
+* Server type and version:
+* Operating System and version:
+* Link to your project:

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,61 @@
+---
+name: Bug Report
+about: Create a report to help us improve.
+labels: area:tooling
+
+---
+<!--- Thank you for taking the time to create a Bug Report! -->
+
+<!--- Before creating an issue please make sure you are using -->
+<!--- the latest version of our software, if possible. -->
+
+<!--- Provide a general summary of the issue in the title above. -->
+
+## Readiness Checklist
+<!--- Please answer the following questions for yourself before -->
+<!--- submitting an issue, and put an `x` in all the boxes that -->
+<!--- apply. -->
+- [ ] I am running the latest version
+- [ ] I checked the documentation and found no answer
+- [ ] I checked to make sure that this issue has not already been filed
+- [ ] I am reporting the issue to the correct repository (for multi-repository projects)
+
+## Expected Behavior
+<!--- If you're describing a bug, tell us what should happen. -->
+
+## Current Behavior
+<!--- If describing a bug, tell us what happens instead of the -->
+<!--- expected behavior.  Who is affected by this bug?  When -->
+<!--- does this occur?  Where does it happen (e.g., run as part -->
+<!--- of automation, run inside a Docker container, etc.)? -->
+<!--- Sometimes it is desirable to include configuration and -->
+<!--- logs, but make to anonymise everything, and remove -->
+<!--- credentials, API tokens, etc., or any other sensitive -->
+<!--- information from everything you decide to include. -->
+
+## Possible Solution
+<!--- Not obligatory, but suggest a fix for the bug, or ideas -->
+<!--- how to implement the addition or change. -->
+
+## Steps to Reproduce
+<!--- Provide a link to a live example, or an unambiguous set -->
+<!--- of steps to reproduce this bug.  Include a code snippet -->
+<!--- can be used to reproduce the issue. -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this issue affected you?  What are you trying to -->
+<!--- accomplish?  Providing context helps us come up with a -->
+<!--- solution that is most useful in the real world. -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment -->
+<!--- you experienced the bug in. -->
+* Version used:
+* Environment name and version (e.g. Go 1.9):
+* Server type and version:
+* Operating System and version:
+* Link to your project:

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,45 @@
+---
+name: Feature Request
+about: Suggest an idea for this project.
+labels: area:tooling
+
+---
+<!--- Thank you for taking the time to open a Feature Request -->
+<!--- and suggest an idea for this project! -->
+
+<!--- Before suggesting a new feature, take a moment to look -->
+<!--- through the existing Feature Requests and Pull Requests, -->
+<!--- as you might be able to find that a similar idea has -->
+<!--- already been considered and might even be in the works. -->
+
+<!--- Provide a general summary of the issue in the title above. -->
+
+## Overview
+<!--- Describe your idea for a new feature in detail. -->
+
+## Possible Implementation
+<!--- Not obligatory, but suggest a possible implementation, -->
+<!--- or ideas how to implement this new feature. -->
+
+## Testing
+<!--- Please describe in detail how the new feature could -->
+<!--- be tested effectively.  When thinking about testing, -->
+<!--- try to consider different aspects of testing e.g., -->
+<!--- unit testing, integration testing and acceptance -->
+<!--- testing, etc., how these can be applied to ensure -->
+<!--- that the new feature has been properly tested and can -->
+<!--- be maintained as part of the code base long term. -->
+
+## Context
+<!--- How lack of this feature affected you?  What are you trying -->
+<!--- to solve?  What is the use case?  What alternatives have you -->
+<!--- considered?  Providing context helps us come up with a -->
+<!--- solution that is most useful in the real world. -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment -->
+<!--- to which this new feature would be applicable (e.g., -->
+<!--- run under automation, executed ad-hoc, etc.), or -->
+<!--- anything else of relevance about your environment -->
+<!--- (e.g., your operating system, versions you current -->
+<!--- run, security requirements, etc.). -->

.github/ISSUE_TEMPLATE/GENERIC_QUESTION.md

@@ -0,0 +1,20 @@
+---
+name: Generic Question
+about: Not a Bug Report or a Feature Request? Ask a question.
+labels: area:tooling
+
+---
+<!--- Thank you for taking the time to ask us a question! -->
+
+<!--- Before asking a question, take a moment to look through the -->
+<!--- existing Bug Reports, Feature Requests and Pull Requests, -->
+<!--- as you might be able to find an answer to your question -->
+<!--- there. -->
+
+## Question
+<!--- When thinking about a new feature or functionality, consider -->
+<!--- opening a Feature Request instead.  If you want to describe -->
+<!--- an unexpected behaviour or an issue you are seeing, then -->
+<!--- consider opening a Bug Report instead.  For anything else -->
+<!--- feel free to ask here, but please keep your question clear -->
+<!--- and concise. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,38 @@
+<!--- Provide a general summary of your changes in the title above. -->
+
+## Description
+<!--- Describe your changes in detail. -->
+
+## Related Issues
+<!--- This project only accepts pull requests related to open issues. -->
+<!--- If suggesting a new feature or change, please discuss it in an -->
+<!--- issue first.  If fixing a bug, there should be an issue describing -->
+<!--- it with steps to reproduce.  Please link to the any related issues -->
+<!--- here: -->
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes.  Include -->
+<!--- details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Types of Changes
+<!--- What types of changes does your code introduce? Put an `x` in -->
+<!--- all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Refactoring (improves code quality but has no user-facing effect)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+- [ ] Documentation
+
+## Readiness Checklist
+<!--- Go over all the following points, and put an `x` in all the boxes -->
+<!--- that apply.  If you're unsure about any of these, don't hesitate -->
+<!--- to ask. We're here to help! -->
+- [ ] My code follows the code style of this project
+- [ ] My change requires a change to the documentation
+- [ ] I have updated the documentation accordingly
+- [ ] I have added tests to cover my changes
+- [ ] All new and existing tests passed

.gitignore

@@ -0,0 +1,5 @@
+bin
+vendor
+dist
+reports
+.idea/

.golangci.yml

@@ -0,0 +1,67 @@
+issues:
+  max-issues-per-linter: 0
+  max-same-issues: 0
+
+linters:
+  enable-all: true
+  disable:
+    - dupl
+    - lll
+    - gochecknoglobals
+    - gochecknoinits
+    - scopelint
+    - funlen
+
+linters-settings:
+  errcheck:
+    exclude: build/errcheck-exclusions.txt
+  govet:
+    check-shadowing: false
+
+  gofmt:
+    simplify: true
+
+  golint:
+    min-confidence: 0
+
+  gocyclo:
+    # minimal code complexity to report, 30 by default (we should lower it to around 15-17)
+    min-complexity: 20
+
+  maligned:
+    # print struct with more effective memory layout or not, false by default
+    suggest-new: true
+
+  misspell:
+    locale: neutral
+
+  goimports:
+    local-prefixes: github.com/elastic/ecctl
+
+  gocritic:
+    enabled-tags:
+      - performance
+      - style
+      - experimental
+    disabled-checks:
+      - hugeParam
+
+issues:
+  # Excluding configuration per-path, per-linter, per-text and per-source
+  exclude-rules:
+    - path: _test\.go
+      linters:
+        - gocyclo
+        - errcheck
+        - dupl
+        - gosec
+    - path: cmd/platform/enrollment-token/command.go
+      linters:
+        - gosec
+    - path: cmd/version.go
+      linters:
+        - gosec
+
+
+output:
+  format: tab

.goreleaser.yml

@@ -0,0 +1,70 @@
+project_name: ecctl
+before:
+  hooks:
+    ## TODO: Remove the GITHUB_TOKEN before going public.
+    - git config --global url."https://${GITHUB_TOKEN}:[email protected]/".insteadOf "https://github.com/"
+    - go mod download
+release:
+  github:
+    owner: elastic
+    name: ecctl
+  name_template: '{{.Tag}}'
+  draft: false
+brews:
+  - github:
+      owner: elastic
+      name: homebrew-ecctl
+    ## TODO: Remove this two directives before going public.
+    download_strategy: EcctlDownloadStrategy
+    custom_require: ./scripts/custom_download_strategies.rb
+    commit_author:
+      name: elasticloudbot
+      email: [email protected]
+    homepage: "https://github.com/elastic/ecctl"
+    description: Elastic Cloud Control, the official Elastic Cloud and ECE command line interface
+    install: |
+      bin.install "ecctl"
+      system "#{bin}/ecctl", "generate", "completions", "-l", "#{var}/ecctl.auto"
+    caveats: |
+      Make sure to source #{var}/ecctl.auto for autocompletions
+      If you have previously built ecctl from source, make sure you've removed that 
+      binary from any directory that has been added to your user $PATH.
+    test: system "#{bin}/ecctl version"
+    folder: Formula
+builds:
+- main: .
+  env:
+    - CGO_ENABLED=0
+  goos:
+    - linux
+    - darwin
+  goarch:
+    - amd64
+    - "386"
+  ignore:
+    - goos: darwin
+      goarch: 386
+  ldflags: -s -w -X main.version={{.Env.VERSION }} -X main.commit={{.Commit}} -X main.owner={{.Env.OWNER}} -X main.repo={{.Env.REPO}}
+  binary: ecctl
+  lang: go
+archives:
+  - name_template: '{{ .ProjectName }}_{{ .Env.VERSION }}_{{ .Os }}_{{ .Arch }}{{ if .Arm}}v{{ .Arm }}{{ end }}'
+    format: tar.gz
+    files:
+    - LICENSE*
+    - README*
+    - docs/*
+snapshot:
+  name_template: SNAPSHOT-{{ .Commit }}
+nfpms:
+  - name_template: "{{ .ProjectName }}_{{ .Env.VERSION }}_{{ .Os }}_{{ .Arch }}"
+    license: Apache 2.0
+    replacements:
+      amd64: 64-bit
+      "386": 32-bit
+    formats:
+      - deb
+      - rpm
+checksum:
+  name_template: '{{ .ProjectName }}_{{ .Env.VERSION }}_checksums.txt'
+dist: dist