terraform-provider | This repo has been deprecated and please | Infrastructure Automation library

You are also missing a Create for this API endpoint. With only Update and Read supported, you will need to extend Create to be the same as Update except for additionally adding the resource to the state. You can easily invoke the Update function within the Create function for this behavior.

For the delete function, this should actually be easier than you may expect. The Terraform provider SDKv2 and your resource code should automatically Read the resource prior to attempting the delete to verify that it actually exists (this probably requires no extra effort on your part without seeing the code). Then you would need to remove the resource from the state with d.SetId("") where d is of type *schema.ResourceData. However, this also automatically is invoked assuming the Delete returns no errors. Therefore, you could define a Delete that merely returns warnings or errors of an appropriate Go type. If you do not need that (and probably would not considering the minimal functionality), then you could probably just return nil. Part of this is speculation based on what your code probably looks like, but in general this all holds true.

Your are missing filter in the rule:

This often happens when one accidentally specifies "hashicorp/azure" instead of "hashicorp/azurerm" in the required_providers block. Did you check the "vm" module referenced in the "azure_instance" module calls? There might be an erroneous "hashicorp/azure" specified there.

I was able to successfully create the lambda function and IAM role resources;

The hashicorp/aws provider must send requests to the AWS API that are signed using the AWS Signature Version 4 algorithm.

One of the goals of the AWS signing scheme is to minimize the time window that a compromised signature couuld be reused by an attacker. To achieve that, the signature scheme includes a timestamp when the signature was created and the remote system requires that the timestamp be within 15 minutes of the request time as understood by the remote system.

The official documentation describes this as follows, at the time I'm writing this:

• Protect against reuse of the signed portions of the request – The signed portions (using AWS Signatures) of requests are valid within 15 minutes of the timestamp in the request. An unauthorized party who has access to a signed request can modify the unsigned portions of the request without affecting the request's validity in the 15 minute window. Because of this, we recommend that you maximize protection by signing request headers and body, making HTTPS requests to Amazon S3, and by using the s3:x-amz-content-sha256 condition key (see Amazon S3 Signature Version 4 Authentication Specific Policy Keys) in AWS policies to require users to sign Amazon S3 request bodies.

If your local system has an incorrect system time or if your system believes its local time to be in a different timezone than you are actually working in then the AWS SDK (which the Terraform AWS provider is built with) will generate a timestamp outside of the allowed 15 minute window, and so your request will fail. This would be true of any request to AWS APIs using this standard signature scheme, whether made by Terraform's AWS provider or by any other AWS-integrated tool.

In order for requests to succeed your system must be able to generate a correct UTC-referenced timestamp. In order for that to be true, it must have both a correct time and – if you are using an operating system like Windows where the system time is stored in local time rather than UTC – a correct configuration of your system time's offset from UTC so that the SDK can convert to a UTC timestamp as the AWS API requires.

I think the "set of map of string" part of this error message is the important part: for_each requires either a map directly (in which case the map keys become the instance identifiers) or a set of individual strings (in which case those strings become the instance identifiers).

Your example YAML file shows yaml_users being defined as a YAML sequence of maps, which corresponds to a tuple of objects on conversion with yamldecode.

To use that data structure with for_each you'll need to first project it into a map whose keys will serve as the unique identifier for each instance of the resource. Assuming that the name values are suitably unique, you could project it so that those values are the keys:

I have found the issue. At the URL I was using the IP address of the Vcloud api, and for some reason terraform didn't like that and was causing the crash, after changing to the FQDN, terraform started working again.

Kind regards

Updated:

A ${ ... } sequence is an interpolation in Terraform's configuration language, which evaluates the expression given between the markers. Unix shells typically use $..

As per the official documentation, the command is evaluated in a shell, and can use environment variables or Terraform variables. So, basically, what you are trying to achieve should work fundamentally.

I did a quick test and I was able to successfully apply that locally:

with double quotes

I just faced a similar issue, and here is what worked for me: