You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Variables can be deprecated through the `deprecated` attribute. If set the variable
will emit a diagnostic if a values is passed to it. This entails both root level and
module variables.
Outputs can be deprecated through the `deprecated` attribute as well. If set wherever
the value is used a diagnostic will be emitted. Root level outputs can not be deprecated.
The only acceptable usage of a deprecated output is another deprecated output (forwarding
the deprecation to the module user).
If modules not under your control have deprecation warnings you can add a `suppress_deprecations_warnigns`
attribute to the module call in question to silence any deeply nested warnings.
body: You can set a `deprecated` attribute on variable and output blocks to indicate that they are deprecated. This will produce warnings when passing in a value for a deprecated variable or when referencing a deprecated output.
Summary: "Invalid value for ignore_nested_deprecations",
176
+
Detail: "The value for ignore_nested_deprecations must be a static boolean (true or false).",
177
+
Subject: attr.Expr.Range().Ptr(),
178
+
})
179
+
}
180
+
181
+
ifval.Type() !=cty.Bool {
182
+
diags=append(diags, &hcl.Diagnostic{
183
+
Severity: hcl.DiagError,
184
+
Summary: "Invalid type for ignore_nested_deprecations",
185
+
Detail: fmt.Sprintf("The value for ignore_nested_deprecations must be a boolean (true or false), but the given value has type %s.", val.Type().FriendlyName()),
186
+
Subject: attr.Expr.Range().Ptr(),
187
+
})
188
+
}
189
+
190
+
mc.IgnoreNestedDeprecations=val.True()
191
+
}
192
+
166
193
varseenEscapeBlock*hcl.Block
167
194
for_, block:=rangecontent.Blocks {
168
195
switchblock.Type {
@@ -278,6 +305,9 @@ var moduleBlockSchema = &hcl.BodySchema{
0 commit comments