terraform/internal/backend
Nick Fagerlund ab70879b9b Remote backend: Stop setting message when creating runs
Historically, we've used TFC's default run messages as a sort of dumping
ground for metadata about the run. We've recently decided to mostly stop
doing that, in favor of:

- Only specifying the run's source in the default message.
- Letting TFC itself handle the default messages.

Today, the remote backend explicitly sets a run message, overriding
any default that TFC might set. This commit removes that explicit message
so we can allow TFC to sort it out.

This shouldn't have any bad effect on TFE out in the wild, because it's
known how to set a default message for remote backend runs since late 2018.
2021-06-09 11:07:39 -07:00
..
init Move tfdiags/ to internal/tfdiags/ 2021-05-17 14:09:07 -07:00
local backend/local: Fix lock when applying stale plan 2021-05-26 16:05:58 -04:00
remote Remote backend: Stop setting message when creating runs 2021-06-09 11:07:39 -07:00
remote-state Move states/ to internal/states/ 2021-05-17 14:09:07 -07:00
backend.go Move terraform/ to internal/terraform/ 2021-05-17 14:09:07 -07:00
backend_test.go Move backend/ to internal/backend/ 2021-05-17 14:09:07 -07:00
cli.go Move terraform/ to internal/terraform/ 2021-05-17 14:09:07 -07:00
operation_type.go Move backend/ to internal/backend/ 2021-05-17 14:09:07 -07:00
operationtype_string.go Move backend/ to internal/backend/ 2021-05-17 14:09:07 -07:00
testing.go Move states/ to internal/states/ 2021-05-17 14:09:07 -07:00
unparsed_value.go Move terraform/ to internal/terraform/ 2021-05-17 14:09:07 -07:00
unparsed_value_test.go Move terraform/ to internal/terraform/ 2021-05-17 14:09:07 -07:00