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

r/azurecaf_name: recreation of dependent resources on resource_types update #140

Open
t3mi opened this issue Dec 6, 2021 · 6 comments · May be fixed by #203
Open

r/azurecaf_name: recreation of dependent resources on resource_types update #140

t3mi opened this issue Dec 6, 2021 · 6 comments · May be fixed by #203
Assignees
@LaurentLesle

Comments

@t3mi
Copy link
Contributor

t3mi commented Dec 6, 2021

I'm using single resource azurecaf_name with resource_types limited to the ones required by module. When new resource is added and resource_types updated to include the new type - terraform triggers to recreate everything, even already deployed resources. Any chance such behavior could be changed to allow updates to the property?
@ofbjansen
Copy link

I have the same "problem" and always end up me doing a terraform apply targeting the caf resource.

@Nepomuceno
Copy link
Contributor

This will be changed in verseion 3.0 it should be released in the comming weeks if not days :)

@sorenhuus
Copy link

This still seems to be an issue.

Any news on when it is expected to be fixed?

@owenfarrell owenfarrell mentioned this issue Oct 13, 2022
Closed
7 tasks
@owenfarrell owenfarrell linked a pull request Nov 2, 2022 that will close this issue
Open
7 tasks
@BlauerPulli
Copy link

Any updates here? Would be nice if the referenced PR could be merged..

@dgonzalezp
Copy link

Same issue here, any updates on this? Thanks!

@patpicos
Copy link

be changed in version 3.0 it should be released in the coming weeks

Will this be backported to 1.x stream?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LaurentLesle LaurentLesle

Labels
None yet
Projects
None yet
Milestone
No milestone
8 participants
@Nepomuceno @LaurentLesle @sorenhuus @t3mi @BlauerPulli @dgonzalezp @patpicos @ofbjansen