Support Build Watch Path Config for pages

[MiguelsPizza]

Confirmation

• [X] This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
• [X] I have searched the issue tracker and my issue isn't already found.
• [X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

https://developers.cloudflare.com/pages/configuration/build-watch-paths#build-watch-paths

Build watch paths is not currently in the pages config schema while it exists in the UI. This is a really nice feature for monorepos so adding support would be great

Affected resource(s)

Terraform configuration files

'n/a'

Link to debug output

https://github.com/cloudflare/terraform-provider-cloudflare/blob/fac029042358006df338fcd6cc749f99734d288d/internal/sdkv2provider/schema_cloudflare_pages_project.go#L12

Panic output

'N/A'

Expected output

'n/a'

Actual output

'n/a'

Steps to reproduce

'n/a'

Additional factoids

func resourceCloudflarePagesProjectSchema() map[string]*schema.Schema {
    buildConfig := schema.Resource{
        Schema: map[string]*schema.Schema{
            "build_caching": {
                Type:        schema.TypeBool,
                Description: "Enable build caching for the project.",
                Optional:    true,
            },
            "build_command": {
                Type:        schema.TypeString,
                Description: "Command used to build project.",
                Optional:    true,
            },
            "destination_dir": {
                Type:        schema.TypeString,
                Description: "Output directory of the build.",
                Optional:    true,
            },
            "root_dir": {
                Type:        schema.TypeString,
                Description: "Your project's root directory, where Cloudflare runs the build command. If your site is not in a subdirectory, leave this path value empty.",
                Optional:    true,
            },
            "web_analytics_tag": {
                Type:        schema.TypeString,
                Description: "The classifying tag for analytics.",
                Optional:    true,
            },
            "web_analytics_token": {
                Type:        schema.TypeString,
                Description: "The auth token for analytics.",
                Optional:    true,
            },
        },

        //should go here?
    }

References

No response

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions[bot]]

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

[jacobbednarz]

closing as a feature request. please lodge these with your account team or support to use the existing feature request process.