pseudo-dynamic / pseudodynamic.terraform.toolset Goto Github PK

Implement the ability to import resources.

The problem: From only the string "Id", that can represent an identifier, JSON or whatever fits in a string, the protocol allows you to send more than one resources to send back.

I need to evaluate the import behaviour, whether more than one resources sending back results into the same amount of ReadResource calls.

As the scenarios get more and more complex, we need a unit testing library for bootstrapping Terraform more easily. The requirement is to make it consumable by users of PseudoDynamic.Terraform.Plugin.Sdk.

Not only unit testing should be made possible but also integration tests*¹ (see here) and acceptance tests*² (see here).

*¹ Integration tests are those tests where you create a plugin server instance inside the same process as the running test where you can mock parts of the plugin server.

*² Acceptance tests are those tests where you create an process-indepdent plugin server instance and checks the reality after running Terraform against the plugin server.

TODO:

• Fix a bug where Terraform command wrapper produces defragmented output and error messages
• Create the PseudoDynamic.Terraform.Plugin.UnitTesting project with at least a Terraform command wrapper and minimal integration and acceptance test capabilities
• Create an integration for creating HCL files specific to one scenario that gets executed against written integration tests or acceptance tests (maybe CDKTF?)

Currently you can write Terraform providers in C#, but currently there exists no workflow to create artifacts that can can be recognized by Terraform registry.

What needs to be done:

• Check rules and constraints for artifacts that get produced by Goreleaser, uploaded as GitHub artifacts and finally recognized by Terraform registry
• Checkout .NET supported runtimes and identify what is not supported

References:

• https://github.com/hashicorp/terraform/blob/main/website/docs/internals/provider-registry-protocol.mdx
• https://developer.hashicorp.com/terraform/tutorials/providers/provider-release-publish?in=terraform%2Fproviders

Currently older versionized resources cannot be upgraded.

The problem: Instead of MessagePack we get JSON. This forces us to write a JSON decoder next to the existing MessagePack decoder.

Currently you cannot use int? or other Nullable<>-wrappable primitives inside a schema. So you cannot use int? to indicate a block attribute or object attribute as optional.

• Nullable<> must be part of type dependency graph
• MessagePack encoder must be rewritten to be generic aware for preventing boxing Nullable<>
• MessagePack encoder must support Nullable<>
• MessagePack decoder must support Nullable<>

Here are some facts that must be taken into account:

• ITerraform<> can contain Nullable<>, but Nullable<> never ITerraform<>
• Nullable<> can contain primitives and BigInteger
• We have a to decode/encode ITerraform<Nullable<>> properly

Currently you are not able to represent Terraform tuples in C# schema classes.

What needs to be done:

• Extend BlockBuilder by TupleDefinition
• Introduce C# attributes for correctly annotating properties to reflect the position of tuple elements
• Reflect new encoding and decoding behaviour in Trancoding/*.cs

As you can see there exists many issues labeled as enhancement. By giving a thump up 👍 you can help to prioritize one issue over the other.

If you cannot wait any longer, pleas let me know if you want to grab an issue by writing to that issue, so I can get back to you and clarify questions if you have any.