feat: Allow passing build_args for building with docker-build module

[michaelhelmick]

Description

The docker provider allows build_args nested in the build map of it's docker_registry_image resource.

https://registry.terraform.io/providers/kreuzwerker/docker/latest/docs/resources/registry_image#nested-schema-for-build

I've found use case to pass build args via Terraform to build a docker image.

Motivation and Context

Working a project that needs build_args passed and think this is a great addition for anybody to use.

Breaking Changes

None.

How Has This Been Tested?

• I have tested and validated these changes using one or more of the provided examples/* projects
  I pushed a docker image to an ECR registry via Terraform using my branch as a source. I passed build_args in the implementation and in the Dockerfile added ARG TESTING_ARGS and set it to ENV TESTING_ARGS $TESTING_ARGS and in the Dockerfile RUN echo $TESTING_ARGS

That showed the following output after I pulled it, ran it and did a docker history

d17c32899430   3 minutes ago   /bin/sh -c echo $TESTING_ARGS                     0B
fd07cea0f973   3 minutes ago   /bin/sh -c #(nop)  ENV TESTING_ARGS =testtttt123   0B
74c1df86fcd3   3 minutes ago   /bin/sh -c #(nop)  ARG TESTING_ARGS               0B

[antonbabenko]

Looks good. Can you also update the code in the examples to show build_args for real, and run pre-commit run -a to update the documentation?

[michaelhelmick]

Should there be a certain version of tfdocs I'm going against? Wants to add "n/a" in a lot of places.

Example

[antonbabenko]

Yes, we stuck with terraform-docs 0.13.0 for the time being. Sorry that I didn't make it clear at first.

[michaelhelmick]

@antonbabenko I switched to 0.13.0 and reran pre-commit run -a and got the same result :( adding "n/a" in a lot of places.

[antonbabenko]

No problems, push it all with other changes and I will fix the docs.

[michaelhelmick]

Thanks!

[antonbabenko]

Thanks, @michaelhelmick !

v2.23.0 has been just released.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.