I'm looking for a developer to build an automated workflow that creates YAML files in our existing GitHub Enterprise (GHE) repository by processing data submitted through a Jira form. The entire system will be deployed on Google Cloud Platform (GCP). Here's a detailed breakdown of what I need: 1. Core Objective To automate the creation of specific YAML configuration files in our GHE repository, triggered by a custom Jira form submission, with the automation hosted on GCP. 2. Technology Stack & Environment · Cloud Platform: Google Cloud Platform (GCP) · Repository: GitHub Enterprise (GHE) - on-premise/private instance · CI/CD/Orchestration: Open to recommendations (Cloud Functions, Cloud Run, or a dedicated Compute Engine instance) · Scripting: Python (preferred) or Node.js · Secret Management: Google Secret Manager 3. High-Level Workflow 1. Form Submission: User fills out a structured Jira form. 2. Trigger: Jira webhook sends payload to our GCP endpoint. 3. Validation & Logic: GCP service validates inputs and applies business logic. 4. Repo Action: Service authenticates with GHE API, creates branch/PR with YAML file. 5. Ticket Creation: A dedicated "Tracker" Jira ticket is automatically created with PR details. 6. Notification: PR details posted back to Jira, with relevant team members tagged. 4. Detailed Requirements A. Jira Form & Inputs · Form must capture: · File Name (e.g., my-service-config.yaml) · API Name (Logical identifier) · Resource Allocation (CPU, Memory values) · Critical Validation: System must have default resource thresholds (configurable). · If requested resources exceed defaults, form must require "Approval Reference" field (approval ticket ID). · Additional custom inputs to be discussed (will share YAML template structure). B. GCP-based Automation Service · Service must be hosted on GCP (preferably serverless - Cloud Functions/Cloud Run). · Must handle: 1. Jira webhook reception and payload parsing 2. Resource validation and approval reference checking 3. YAML template population using form data 4. GHE API authentication (using GitHub App or PAT stored in Secret Manager) 5. Git operations: create branch, commit file, open PR in GHE repo 6. Extract PR URL, number, and commit hash C. GHE-Specific Considerations · Must work with GitHub Enterprise API v3/v4 (not public GitHub.com) · Authentication must work with our private GHE instance (likely using GitHub App installation tokens or fine-grained PATs) · Repository access patterns may differ from public GitHub D. Jira Ticket Automation · Automatically create a new Jira tracker ticket with: · PR link (to GHE repository) · Commit hash · Approval reference (if applicable) · Automatically tagged assignee (logic based on team/resource type) 5. Deliverables 1. Source code for GCP-hosted service (Python/Node.js) 2. GCP deployment configuration (Terraform or deployment script) 3. Setup instructions for: · Jira webhook configuration · GHE App creation/configuration · Google Secret Manager setup 4. Documentation on adjusting: · Default resource thresholds · Tagging logic · YAML template 5. Test suite demonstrating complete flow 6. Open Points for Discussion I'd like to schedule a brief call to discuss: · The exact YAML template structure and additional form fields · GHE authentication method (GitHub App vs. PAT) · Specific tagging logic for the automated Jira assignment · Error handling and logging strategy in GCP 7. Preferred Qualifications · Experience with GCP serverless services (Cloud Functions, Cloud Run) · Experience with GitHub Enterprise API (not just public GitHub) · Familiarity with Jira webhooks and REST API · Python/Node.js development experience · Understanding of Git operations via API Please let me know your experience with similar GCP+GHE integrations and your proposed approach for this project. Looking forward to your proposal.