docs: remove non-usable workflow type in ami_imagebuilder_workflow resource

[stefanfreitag]

Description

The documentation of the resource ami_imagebuilder_workflow mentions for the argument type

Valid values: BUILD, TEST, DISTRIBUTION.

Image Builder handles the workflow type DISTRIBUTION, it cannot be configured by users. When trying to do so, for example using the code snippet provided as part of #39785

resource aws_imagebuilder_workflow codebuild-projects {
  name = "CodeBuildProjectsDistributionWorkflow"
  version = "1.0.0"
  type = "DISTRIBUTION"
  data = file("${path.module}/codebuild-projects-distribution.workflow.yaml")
}

the API returns the error The value supplied for parameter 'type' is not valid. Custom distribution workflows are not supported.

This pull request is to update the documentation for the resource. Jared Baker provided an idea for the required change:

Removing the DISTRIBUTION valid value from the docs, or explicitly stating it is only for internal Image Builder workflows provides guidance that it’s not usable. I

Relations

• Closes [Bug]: aws_imagebuilder_workflow allows invalid value "DISTRIBUTION" for 'type' argument #39785 (original issue)
• fix: update validation for image builder workflow type #39810 (my first try, updating also the validation function), already closed.

References

Here I explained the current situation.

Output from Acceptance Testing

Not required. Only documentation changed.

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.