Setting a cloudbuild trigger from enterprise self hosted github

[chitha20]

Current Problem :

Hi with the recent GA'ed of cloudbuild private github enterprise feature as mentioned here ,

we would like to leverage terraform automation in configuring the trigger for cloudbuild job from self hosted github. Current provider doc here

Right now the below terraform snippet tried to create a trigger from github which expects like this :

github.com/my-org/my-repo

And it fails for our case as we want to have capability to change the github.com towards self hosted github url.

resource "google_cloudbuild_trigger" "my-resources" {
  github {
    name  = "my-repo
    owner = "my-org"

    push {
      branch       = "^master$"
      invert_regex = false
    }
  }

  filename = "cloudbuild.yaml"
} 

Expected outcome :

We should have ability to configure the self hosted github_url in google_cloudbuild_trigger github section of the provider.

Let us know if there is a support for it already or if thats upcoming.

[rileykarson]

I think this is a matter of adding both a resource for https://cloud.google.com/build/docs/api/reference/rest/v1/projects.githubEnterpriseConfigs#GitHubEnterpriseConfig and the enterpriseConfigResourceName field to trigger. The API guide is confusing, and talks about creating JSON files and pushing them using curl rather than using a language client.

[NaurisSadovskis]

hey folks, any update on this?

[nickozilla]

Hi is anyone working on this?

[itsavvy-ankur]

Hi, I have recently stumbled on this as well. Just wondering if this is being worked upon or any workarounds exist for creating the trigger for GitHub enterprise repositories?

[sebxgd]

I have same issue

[ramiresdallago]

Hi, same issue here! Any news?

[prateek2408]

Working on it.

[kuba-vodafone]

anyone knows when this change will be included in the release?

[rileykarson]

Likely next ~Monday's~ Tuesday's release (delayed due to a holiday)

[kuba-vodafone]

hello,

do you know when today's release is expected?

[rileykarson]

Hmm- didn't look like it happened. I'll follow up w/ the release owner tomorrow (we're past their core hours right now).

[parmus]

We are also eagerly awaiting this next release.

[github-actions[bot]]

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.