sourcegraph/dev/managedservicesplatform/spec
Robert Lin 6c59b02534
feat/msp: do not use tfvars file outside of deploy-type 'subscription' (#62704)
Closes CORE-121

The dependency on the generated `tfvars` file is frustrating for first-time MSP setup because it currently requires `-stable=false` to update, and doesn't actually serve any purpose for deploy types other than `subscription` (which uses it to isolate image changes that happen on via GitHub actions). This makes it so that we don't generate, or depend on, the dynamic `tfvars` file unless you are using `subscription`.

I've also added a rollout spec configuration, `initialImageTag`, to make the initial tag we provision environments with configurable (as some services might not publish `insiders` images) - see the docstring.

## Test plan

Inspect output of `sg msp generate -all`
2024-05-16 09:43:47 -07:00
..
BUILD.bazel bazel: transcribe test ownership to bazel tags (#62664) 2024-05-16 15:51:16 +01:00
build.go msp: generate projectID up-front and persist in spec (#59220) 2023-12-22 17:25:40 -08:00
environment_test.go feat/msp: do not use tfvars file outside of deploy-type 'subscription' (#62704) 2024-05-16 09:43:47 -07:00
environment.go feat/msp: do not use tfvars file outside of deploy-type 'subscription' (#62704) 2024-05-16 09:43:47 -07:00
monitoring.go sg/msp: make nobl9 key optional in spec (#60511) 2024-02-14 13:32:23 +00:00
projectid.go msp: generate projectID up-front and persist in spec (#59220) 2023-12-22 17:25:40 -08:00
rollout.go feat/msp: do not use tfvars file outside of deploy-type 'subscription' (#62704) 2024-05-16 09:43:47 -07:00
service_test.go msp: support custom project-level iam config (#57905) 2023-10-26 08:43:45 -07:00
service.go msp: update msp-ops links (#62435) 2024-05-06 10:36:15 -07:00
spec.go msp/spec: exclude populated README from YAML (#62215) 2024-04-26 20:47:09 +00:00