public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: kdevops@lists.linux.dev
Subject: Re: [PATCH] Makefile: terraform wasn't building the kdevops_nodes file
Date: Thu, 2 Oct 2025 22:38:48 +0200	[thread overview]
Message-ID: <485cd40b-981e-4032-bac2-471a86ba4927@kernel.org> (raw)
In-Reply-To: <20251002201338.3592784-1-cel@kernel.org>



On 02/10/2025 22.13, Chuck Lever wrote:
> From: Daniel Gomez <da.gomez@kernel.org>
> 
> When "make bringup" runs "terraform plan", it complains that the
> kdevops_nodes variable isn't set.
> 
> extra_vars.yaml does contain the variable, but I'm guessing that
> somehow gen_nodes runs after gen_tfvars now? Not really sure.
> 
> Daniel suggests:
>> I think it'd be best to move KDEVOPS_NODES just after we assign
>> the filename to it (provision.Makefile -> guestfs.Makefile):
> 
> Fixes: 5457b742d611 ("Makefile: fix target dependency order")
> Signed-off-by: Daniel Gomez <da.gomez@kernel.org>
> ---
>  Makefile | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> Daniel, I've totally lost the plot. Is this patch adequate for fixing
> the "terraform plan" failures, or do you have something else in mind?

Yes, that is correct becuase we want/need to fill DEFAULT_DEPS after
KDEVOPS_NODES is generated.

And sorry if I made it so confusing!

      reply	other threads:[~2025-10-02 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 20:13 [PATCH] Makefile: terraform wasn't building the kdevops_nodes file Chuck Lever
2025-10-02 20:38 ` Daniel Gomez [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=485cd40b-981e-4032-bac2-471a86ba4927@kernel.org \
    --to=da.gomez@kernel.org \
    --cc=cel@kernel.org \
    --cc=kdevops@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox