Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Usage of kubernetes provider in helm terraform template forces 2 stage apply #77

Open
nhinze23 opened this issue Jun 12, 2024 · 0 comments
Open

Usage of kubernetes provider in helm terraform template forces 2 stage apply #77

nhinze23 opened this issue Jun 12, 2024 · 0 comments

Comments

@nhinze23
Copy link
Contributor

Determining if the setup should be applied the kubernetes provider is used.
If no cluster is available the terraform apply only works in 2 stages where you first use the -target option for the cluster.
This is not possible for coder terraform templates.
nhinze23 added a commit that referenced this issue Jun 12, 2024
@nhinze23
#77 Delete kubernetes provider to determine setup count.
b423877 
Use terraform data for calculating the count implies that terraform needs the cluster to calculate the state.
If the cluster is not available the terraform workflow has to be with 2 stages.
This is not possible for a coder template apply.
nhinze23 added a commit that referenced this issue Jun 12, 2024
@nhinze23
#77 Add prevent destroy option to the bucket and keys
9d4165c
nhinze23 added a commit that referenced this issue Jun 12, 2024
@nhinze23
#77 Delete prevent destroy because it is better to use the option in …
260cc30 
…the module caller.
jelemux added a commit that referenced this issue Jun 14, 2024
@jelemux
#77 use resource patch content instead of file
dce6230
jelemux added a commit that referenced this issue Jun 18, 2024
@jelemux
#77 Update changelog
10cdad3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nhinze23