backend/local: Replace CLI with view instance
This commit extracts the remaining UI logic from the local backend,
and removes access to the direct CLI output. This is replaced with an
instance of a `views.Operation` interface, which codifies the current
requirements for the local backend to interact with the user.
The exception to this at present is interactivity: approving a plan
still depends on the `UIIn` field for the backend. This is out of scope
for this commit and can be revisited separately, at which time the
`UIOut` field can also be removed.
Changes in support of this:
- Some instances of direct error output have been replaced with
diagnostics, most notably in the emergency state backup handler. This
requires reformatting the error messages to allow the diagnostic
renderer to line-wrap them;
- The "in-automation" logic has moved out of the backend and into the
view implementation;
- The plan, apply, refresh, and import commands instantiate a view and
set it on the `backend.Operation` struct, as these are the only code
paths which call the `local.Operation()` method that requires it;
- The show command requires the plan rendering code which is now in the
views package, so there is a stub implementation of a `views.Show`
interface there.
Other refactoring work in support of migrating these commands to the
common views code structure will come in follow-up PRs, at which point
we will be able to remove the UI instances from the unit tests for those
commands.
2021-02-17 19:01:30 +01:00
|
|
|
package views
|
|
|
|
|
|
|
|
import (
|
|
|
|
"bytes"
|
|
|
|
"fmt"
|
|
|
|
"strings"
|
|
|
|
|
|
|
|
"github.com/hashicorp/terraform/command/arguments"
|
|
|
|
"github.com/hashicorp/terraform/command/format"
|
|
|
|
"github.com/hashicorp/terraform/plans"
|
|
|
|
"github.com/hashicorp/terraform/states"
|
|
|
|
"github.com/hashicorp/terraform/states/statefile"
|
|
|
|
"github.com/hashicorp/terraform/terraform"
|
|
|
|
"github.com/hashicorp/terraform/tfdiags"
|
|
|
|
)
|
|
|
|
|
|
|
|
type Operation interface {
|
2021-02-18 23:23:34 +01:00
|
|
|
Interrupted()
|
|
|
|
FatalInterrupt()
|
backend/local: Replace CLI with view instance
This commit extracts the remaining UI logic from the local backend,
and removes access to the direct CLI output. This is replaced with an
instance of a `views.Operation` interface, which codifies the current
requirements for the local backend to interact with the user.
The exception to this at present is interactivity: approving a plan
still depends on the `UIIn` field for the backend. This is out of scope
for this commit and can be revisited separately, at which time the
`UIOut` field can also be removed.
Changes in support of this:
- Some instances of direct error output have been replaced with
diagnostics, most notably in the emergency state backup handler. This
requires reformatting the error messages to allow the diagnostic
renderer to line-wrap them;
- The "in-automation" logic has moved out of the backend and into the
view implementation;
- The plan, apply, refresh, and import commands instantiate a view and
set it on the `backend.Operation` struct, as these are the only code
paths which call the `local.Operation()` method that requires it;
- The show command requires the plan rendering code which is now in the
views package, so there is a stub implementation of a `views.Show`
interface there.
Other refactoring work in support of migrating these commands to the
common views code structure will come in follow-up PRs, at which point
we will be able to remove the UI instances from the unit tests for those
commands.
2021-02-17 19:01:30 +01:00
|
|
|
Stopping()
|
|
|
|
Cancelled(destroy bool)
|
|
|
|
|
|
|
|
EmergencyDumpState(stateFile *statefile.File) error
|
|
|
|
|
|
|
|
PlanNoChanges()
|
|
|
|
Plan(plan *plans.Plan, baseState *states.State, schemas *terraform.Schemas)
|
|
|
|
PlanNextStep(planPath string)
|
|
|
|
|
|
|
|
Diagnostics(diags tfdiags.Diagnostics)
|
|
|
|
}
|
|
|
|
|
|
|
|
func NewOperation(vt arguments.ViewType, inAutomation bool, view *View) Operation {
|
|
|
|
switch vt {
|
|
|
|
case arguments.ViewHuman:
|
|
|
|
return &OperationHuman{View: *view, inAutomation: inAutomation}
|
|
|
|
default:
|
|
|
|
panic(fmt.Sprintf("unknown view type %v", vt))
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
type OperationHuman struct {
|
|
|
|
View
|
|
|
|
|
|
|
|
// inAutomation indicates that commands are being run by an
|
|
|
|
// automated system rather than directly at a command prompt.
|
|
|
|
//
|
|
|
|
// This is a hint not to produce messages that expect that a user can
|
|
|
|
// run a follow-up command, perhaps because Terraform is running in
|
|
|
|
// some sort of workflow automation tool that abstracts away the
|
|
|
|
// exact commands that are being run.
|
|
|
|
inAutomation bool
|
|
|
|
}
|
|
|
|
|
|
|
|
var _ Operation = (*OperationHuman)(nil)
|
|
|
|
|
2021-02-18 23:23:34 +01:00
|
|
|
func (v *OperationHuman) Interrupted() {
|
|
|
|
v.streams.Println(format.WordWrap(interrupted, v.outputColumns()))
|
|
|
|
}
|
|
|
|
|
|
|
|
func (v *OperationHuman) FatalInterrupt() {
|
|
|
|
v.streams.Eprintln(format.WordWrap(fatalInterrupt, v.errorColumns()))
|
|
|
|
}
|
|
|
|
|
|
|
|
const fatalInterrupt = `
|
|
|
|
Two interrupts received. Exiting immediately. Note that data loss may have occurred.
|
|
|
|
`
|
|
|
|
|
|
|
|
const interrupted = `
|
|
|
|
Interrupt received.
|
|
|
|
Please wait for Terraform to exit or data loss may occur.
|
|
|
|
Gracefully shutting down...
|
|
|
|
`
|
|
|
|
|
backend/local: Replace CLI with view instance
This commit extracts the remaining UI logic from the local backend,
and removes access to the direct CLI output. This is replaced with an
instance of a `views.Operation` interface, which codifies the current
requirements for the local backend to interact with the user.
The exception to this at present is interactivity: approving a plan
still depends on the `UIIn` field for the backend. This is out of scope
for this commit and can be revisited separately, at which time the
`UIOut` field can also be removed.
Changes in support of this:
- Some instances of direct error output have been replaced with
diagnostics, most notably in the emergency state backup handler. This
requires reformatting the error messages to allow the diagnostic
renderer to line-wrap them;
- The "in-automation" logic has moved out of the backend and into the
view implementation;
- The plan, apply, refresh, and import commands instantiate a view and
set it on the `backend.Operation` struct, as these are the only code
paths which call the `local.Operation()` method that requires it;
- The show command requires the plan rendering code which is now in the
views package, so there is a stub implementation of a `views.Show`
interface there.
Other refactoring work in support of migrating these commands to the
common views code structure will come in follow-up PRs, at which point
we will be able to remove the UI instances from the unit tests for those
commands.
2021-02-17 19:01:30 +01:00
|
|
|
func (v *OperationHuman) Stopping() {
|
|
|
|
v.streams.Println("Stopping operation...")
|
|
|
|
}
|
|
|
|
|
|
|
|
func (v *OperationHuman) Cancelled(destroy bool) {
|
|
|
|
if destroy {
|
|
|
|
v.streams.Println("Destroy cancelled.")
|
|
|
|
} else {
|
|
|
|
v.streams.Println("Apply cancelled.")
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
func (v *OperationHuman) EmergencyDumpState(stateFile *statefile.File) error {
|
|
|
|
stateBuf := new(bytes.Buffer)
|
|
|
|
jsonErr := statefile.Write(stateFile, stateBuf)
|
|
|
|
if jsonErr != nil {
|
|
|
|
return jsonErr
|
|
|
|
}
|
|
|
|
v.streams.Eprintln(stateBuf)
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
func (v *OperationHuman) PlanNoChanges() {
|
|
|
|
v.streams.Println("\n" + v.colorize.Color(strings.TrimSpace(planNoChanges)))
|
|
|
|
v.streams.Println("\n" + strings.TrimSpace(format.WordWrap(planNoChangesDetail, v.outputColumns())))
|
|
|
|
}
|
|
|
|
|
|
|
|
func (v *OperationHuman) Plan(plan *plans.Plan, baseState *states.State, schemas *terraform.Schemas) {
|
|
|
|
renderPlan(plan, baseState, schemas, &v.View)
|
|
|
|
}
|
|
|
|
|
|
|
|
// PlanNextStep gives the user some next-steps, unless we're running in an
|
|
|
|
// automation tool which is presumed to provide its own UI for further actions.
|
|
|
|
func (v *OperationHuman) PlanNextStep(planPath string) {
|
|
|
|
if v.inAutomation {
|
|
|
|
return
|
|
|
|
}
|
|
|
|
v.outputHorizRule()
|
|
|
|
|
|
|
|
if planPath == "" {
|
|
|
|
v.streams.Print(
|
|
|
|
"\n" + strings.TrimSpace(format.WordWrap(planHeaderNoOutput, v.outputColumns())) + "\n",
|
|
|
|
)
|
|
|
|
} else {
|
|
|
|
v.streams.Printf(
|
|
|
|
"\n"+strings.TrimSpace(format.WordWrap(planHeaderYesOutput, v.outputColumns()))+"\n",
|
|
|
|
planPath, planPath,
|
|
|
|
)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
const planNoChanges = `
|
|
|
|
[reset][bold][green]No changes. Infrastructure is up-to-date.[reset][green]
|
|
|
|
`
|
|
|
|
|
|
|
|
const planNoChangesDetail = `
|
|
|
|
That Terraform did not detect any differences between your configuration and the remote system(s). As a result, there are no actions to take.
|
|
|
|
`
|
|
|
|
|
|
|
|
const planHeaderNoOutput = `
|
|
|
|
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
|
|
|
|
`
|
|
|
|
|
|
|
|
const planHeaderYesOutput = `
|
|
|
|
Saved the plan to: %s
|
|
|
|
|
|
|
|
To perform exactly these actions, run the following command to apply:
|
|
|
|
terraform apply %q
|
|
|
|
`
|