Comments (4)
Can you describe more about the desired outcome? I'm a little confused on the error you're seeing and why it would be a permadiff.
Should the default be no autohealing at all?
from terraform-google-vm.
The desired outcome is that terraform would not suggest a change to the MIG every time I apply. I am not specifying autohealing, but that one variable (initial delay seconds) is causing the definition to show up in the module (which is essentially an empty policy). The provider should ideally complain that it won't create an auto healing policy since it does not have enough of the information, but the module should also not create it by default.
Auto healing should be optional according to tf docs.
from terraform-google-vm.
terraform does not accept the
auto_healing_policies block. keeps repeating block is not expected.
any suggestions?
from terraform-google-vm.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days
from terraform-google-vm.
Related Issues (20)
- Instance Template creates pd-standard disk instead of pd-balanced HOT 1
- Please expose resource_policies as a variable for the instance_template HOT 2
- Autoscaling signal empty condition HOT 1
- modules/umig creates a group per instance if num_instances>1 HOT 1
- Module for `instance_template` fails `terraform validate` in `v9.0.0` release HOT 2
- Add secure tags (resource_manager_tags) on compute_instance module
- Link to project_services module broken HOT 1
- Add support for enable_display and allow_stopping_for_update to compute_instance HOT 1
- B
- Attaching the existing disk in Instance template HOT 1
- Optional object type attributes are experimental: instance_template/variables.tf line 169 HOT 2
- Property "static_ips" isn't use in compute instance HOT 2
- Usage examples missing HOT 1
- Add Support for the source_image field on additional_disks
- Support resource_manager_tags on instance_template module HOT 1
- Upgrade of instance_template and compute_instance from v10.1.1 to v11.1.0 triggers replacement of the VM HOT 1
- 'update_policy' variable for MIG submodule requires parameters that have conflicts. HOT 1
- "most_disruptive_allowed_action" should be optional for update_policy but is required HOT 1
- Are you planning on releasing a new version soon? HOT 2
- Error message in tfvars is not ending with a dot or question mark HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-google-vm.