-
Notifications
You must be signed in to change notification settings - Fork 12
Provide support for passing backend remote state using spk infra generate
#728
Comments
@yradsmikham what the situation with this? |
@andrebriggs, I plan on working on this later this week. The description for this issue is accurate. |
@NathanielRose do you agree with the description? cc @yradsmikham |
@andrebriggs Yes I agree with the description, I was initially unsure whether or not this functionality was in the new Iteration II PR. |
If we are all in agreement here, I can start working on this issue at some point today or tomorrow. Thanks y'all! :) |
Hey, I would like to take this on, But I am realizing due to issues I may be experiencing with the new addition of |
@NathanielRose, you're welcome to work on this! I also agree that this item could be pushed to the next sprint given the amount of the time left in our current sprint. |
As a:
Developer
I want:
spk infra generate
to recursively apply remote state configurations for tfstate files from parent directory to sub-directories for terraform deploymentSo that:
at the final sub-directory, it creates a generated directory and fills the backend tfvars using the backend state variables accumulated from parent and child levels.
Describe the solution you'd like:
Upon generation,
spk infra generate
should:Acceptance Criteria:
When a user runs
spk infra generate east
for example, this should read in the backend configuration in thedefinition.json
of the (parent) current working directory, and then apply the backend configuration of thedefinition.json
of theeast
cluster. It creates agenerated
directory, with abackend.tfvars
with the accumulated variables.Does this require updates to documentation?:
Yes.
The text was updated successfully, but these errors were encountered: