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.

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

remove force new #68

Merged
merged 1 commit into from
Aug 7, 2020
Merged

remove force new #68

merged 1 commit into from
Aug 7, 2020

Conversation

scottwinkler
Copy link
Owner

removing the need for force new on many attributes. also fixing the way error logging works. closes issues #67. #60, #59

@scottwinkler scottwinkler merged commit 3c8cd6a into master Aug 7, 2020
@AdamCoulterOz
Copy link

@scottwinkler I've just noticed that this now causes my resources to force replacement whenever the environment variables change. Is this intended? FYI - @pacon-vib

@scottwinkler
Copy link
Owner Author

My mistake, I'll fix this. You're right it shouldn't be force new because if it changes it is handled by the update function.

@AdamCoulterOz
Copy link

AdamCoulterOz commented Aug 13, 2020

Thanks so much @scottwinkler ... I'm writing a blog post for my company (servian.com) about terraform 0.13 and using a pattern such as your shell provider (and using it as an example) as a much more logical extension mechanism to wrap existing client cli's rather than having to develop a full golang tool chain to make a tiny change. Something terraform core should incorporate a first party way to publish full providers.

It will be published here sometime in the next 3-4 weeks: https://medium.com/weareservian

I've had a go at something a bit rough the last few days here..

https://registry.terraform.io/modules/servian/subscription/azurerm

@jwicks
Copy link

jwicks commented Oct 13, 2020

@scottwinkler Are you still planning to add a fix for the issue @AdamCoulterOz mentioned?

@scottwinkler
Copy link
Owner Author

Sorry I forgot about this. Let me create a new issue to track it. I will get it done in the next few days.

@AdamCoulterOz nice work on the module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants