opctl build should build config.yaml and pull the manifests

[aleksandrmelnikov]

and pull the correct manifests based on params.yaml. The use case here is that a user should be able to download a params.yaml file from git (encrypted) or a key vault service and be able to deploy/update the cluster

Thursday, June 25, 2020 - 01_55_35 PM
For opctl init, we should warn the user if they already have params.yaml existing.

• It'll warn them that this operation is destructive
• They have to pass --force to over-write existing params.yaml

Tuesday, June 30, 2020 - 12_18_11 PM
Validate the params.yaml before running build or apply.

• Version 0.11.0 of CLI will know about application.provider
• Version 0.10.0 will not

So when apply is run on 0.11.0, it will check params.yaml.
It sees application. It checks for application.fqdn, application.insecure, and application.provider (plus others, prior are examples).
It sees provider missing, it throws an error with the value. Points user to docs.

Add breaking changes log

[issue-label-bot]

Issue-Label Bot is automatically applying the label kind/bug to this issue, with a confidence of 0.57. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.