From fde62775651a89ba7448e50b446c3045db1f5ab2 Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Wed, 14 Feb 2024 17:13:22 -0800 Subject: [PATCH] stackruntime: Pass ExperimentsAllowed into stackeval for apply This was originally part of 7dad938fdb6bfeaf7cc082ce50bcf99f7889a2a9 but unfortunately seems to have got lost during some rebasing, or some other similar sort of annoying reason. This now allows the "experiments allowed" flag to propagate into the stackeval package when we're running the apply phase, for consistency with all of the other phases. Without this, it's possible to plan a configuration that's participating in experiments, but then it fails in a strange way during the apply step due to Terraform suddenly thinking it's a stable release where experiments are disabled. --- internal/stacks/stackruntime/apply.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/internal/stacks/stackruntime/apply.go b/internal/stacks/stackruntime/apply.go index 1af2733b15..33e78f44ec 100644 --- a/internal/stacks/stackruntime/apply.go +++ b/internal/stacks/stackruntime/apply.go @@ -59,7 +59,8 @@ func Apply(ctx context.Context, req *ApplyRequest, resp *ApplyResponse) { req.Config, req.RawPlan, stackeval.ApplyOpts{ - ProviderFactories: req.ProviderFactories, + ProviderFactories: req.ProviderFactories, + ExperimentsAllowed: req.ExperimentsAllowed, }, outp, )