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
Using the "Deploy to Oracle Cloud" link. Checking the accept term os use. Get windows with this error.
At least one variable in the schema file can't be parsed. Only successfully parsed variables are rendered. To troubleshoot schema parsing issues, validate against the meta schema (provided in the Resource Manager documentation):
Variable $db_transit_subnet_dns_label declared in .tf file but not found in .yaml file (schema).
Variable $web_lb_subnet_dns_label declared in .tf file but not found in .yaml file (schema).
Variable $web_transit_subnet_dns_label declared in .tf file but not found in .yaml file (schema).
how do I fix this? Is there a new version in the works?
Thank you,
David
The text was updated successfully, but these errors were encountered:
Execution with default settings, and get an additional warning in the Job Log.
Warning: Interpolation-only expressions are deprecated
on data_sources.tf line 54, in data "oci_identity_fault_domains" "fds"
54: availability_domain = "${data.oci_identity_availability_domain.ad.name}"
Terraform 0.11 and earlier required all non-constant expressions to be
provided via interpolation syntax, but this pattern is now deprecated. To
silence this warning, remove the "${ sequence from the start and the }"
sequence from the end of this expression, leaving just the inner expression.
Template interpolation syntax is still used to construct strings from
expressions when the template includes multiple interpolation sequences or a
mixture of literal strings and interpolations. This deprecation applies only
to templates that consist entirely of a single interpolation sequence.
Using the "Deploy to Oracle Cloud" link. Checking the accept term os use. Get windows with this error.
At least one variable in the schema file can't be parsed. Only successfully parsed variables are rendered. To troubleshoot schema parsing issues, validate against the meta schema (provided in the Resource Manager documentation):
Variable $db_transit_subnet_dns_label declared in .tf file but not found in .yaml file (schema).
Variable $web_lb_subnet_dns_label declared in .tf file but not found in .yaml file (schema).
Variable $web_transit_subnet_dns_label declared in .tf file but not found in .yaml file (schema).
how do I fix this? Is there a new version in the works?
Thank you,
David
The text was updated successfully, but these errors were encountered: