Skip to content

Provide a brief, clear description of the bug #6763

@itsomg134

Description

@itsomg134

Description

Bug Report

Summary

Environment

  • Operating System:
  • Go Version:
  • Terraform Version:
  • GitLab Provider Version:
  • GitLab Version: (CE/EE and version number)

Steps to Reproduce

Expected Behavior

Actual Behavior

Configuration Files

VS Code Settings (settings.json)

{
  "go.testEnvVars": {
    "TF_ACC": "1",
    "GITLAB_TOKEN": "glpat-ACCTEST1234567890123",
    "GITLAB_BASE_URL": "http://127.0.0.1:8085"
  },
  "go.testFlags": [
    "-count=1",
    "-v",
    "-tags=acceptance,flakey,settings,saas",
    "-parallel=2",
    "-timeout",
    "180s"
  ],
  "go.buildFlags": [
    "--tags=acceptance,flakey,settings"
  ]
}

Services Configuration (devcontainer.json or similar)

services:
  gitlab-ce:
    name: GitLab-CE Local Container
    description: A locally running GitLab instance, used for acceptance testing
    triggeredBy:
      - manual
    commands:
      start: SERVICE=gitlab-ce make testacc-up
      stop: SERVICE=gitlab-ce make testacc-down
        
  gitlab-ee:
    name: GitLab-EE Local Container
    description: A locally running GitLab instance, used for acceptance testing
    triggeredBy:
      - manual
    commands:
      start: SERVICE=gitlab-ee make testacc-up
      stop: SERVICE=gitlab-ee make testacc-down

tasks:
  getDependencies:
    name: Get Golang Dependencies
    description: Retrieves dependencies for the TF provider to prep the environment
    triggeredBy:
      - postEnvironmentStart
    command: go get

Error Messages/Logs

<!-- Paste any relevant error messages or logs here -->

Screenshots

Additional Context

Possible Solution


Reported by:
Date: October 13, 2025

Steps to reproduce

No response

Excepted behavior

I've created a comprehensive bug report template for you that includes:

Summary section for a quick overview of the issue
Environment details to capture system and version information
Steps to reproduce the bug
Expected vs actual behavior sections
Configuration files with your corrected JSON and YAML configurations already embedded
Error logs section for stack traces or error messages
Screenshots area for visual documentation
Additional context and possible solution sections

You can fill in the relevant sections with the specific details of your bug. The template is formatted in Markdown, making it easy to copy directly into GitHub Issues, GitLab Issues, or any bug tracking system that supports Markdown.

Screenshots

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions