All skills
gogf avatar

/goframe-v2

@911705d
by GoFramegogf/skills81 stars
3

GoFrame v2 development skill. Use only when the target Go project uses or is explicitly adopting GoFrame v2: the nearest go.mod requires github.com/gogf/gf/v2, existing Go files import github.com/gogf/gf/v2 or any github.com/gogf/gf/v2/... component package, or the user asks to scaffold, migrate, or build with GoFrame. Trigger for GoFrame-backed Go work such as APIs/controllers/services, middleware, routing/config, ORM/DAO/DO/entity/database operations, gf CLI/codegen, HTTP/gRPC services, and microservice conventions. Do not trigger for generic Go projects without GoFrame evidence, frontend-only work, shell scripts, or unrelated infrastructure tasks.

Use this Skill: https://skilld.dev/gh/gogf/skills/goframe-v2

This session only. Nothing lands on disk.

examplesconfigkubecmREADME.MD

≈1.2k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Kubernetes ConfigMap Configuration Example

Description

This directory contains an example demonstrating how to integrate Kubernetes ConfigMap with GoFrame applications for configuration management. It shows:

  1. Kubernetes Client Configuration

    • In-Pod configuration setup
    • Out-of-Pod configuration setup
    • ConfigMap access and management
    • Error handling and logging
  2. Configuration Management

    • Configuration loading and parsing
    • Dynamic configuration updates
    • Configuration value retrieval

Directory Structure

.
├── boot_in_pod/     # Bootstrap configuration for in-pod deployment
│   └── boot.go      # In-pod client initialization
├── boot_out_pod/    # Bootstrap configuration for out-of-pod deployment
│   └── boot.go      # Out-of-pod client initialization
├── main.go          # Main application entry
├── go.mod           # Go module file
└── go.sum           # Go module checksums

Requirements

Features

The example showcases the following features:

  1. Kubernetes Integration

    • In-Pod configuration
    • Out-of-Pod configuration
    • ConfigMap management
    • Error handling
  2. Configuration Management

    • Configuration loading
    • Value retrieval
    • Type conversion
    • Default values
  3. Dynamic Updates

    • Configuration watching
    • Change notification
    • Hot reload support

Configuration

Kubernetes Setup

  1. Cluster Configuration:

    • Kubernetes cluster access
    • Namespace management
    • RBAC permissions
  2. ConfigMap Setup:

    • ConfigMap creation
    • Data item management
    • Access control

Client Configuration

  1. In-Pod Settings:

    • Automatic service account
    • ConfigMap name
    • Data item name
  2. Out-of-Pod Settings:

    • KubeConfig path
    • Namespace selection
    • Client configuration
    • Access permissions

Usage

  1. Create ConfigMap:

    # Create a ConfigMap with configuration data
    kubectl create configmap test-configmap --from-file=config.yaml=./config.yaml
  2. Configure Access:

    # Ensure proper RBAC permissions
    kubectl create role config-reader --verb=get,list,watch --resource=configmaps
    kubectl create rolebinding config-reader-binding --role=config-reader --serviceaccount=default:default
  3. Run Example:

    # For in-pod deployment
    go run main.go
    
    # For out-of-pod deployment (local development)
    KUBE_CONFIG=~/.kube/config go run main.go

Implementation Details

  1. In-Pod Setup (boot_in_pod/boot.go):

    • Simple configuration for in-pod deployment
    • Automatic service account usage
    • Minimal configuration required
  2. Out-of-Pod Setup (boot_out_pod/boot.go):

    • External cluster access configuration
    • KubeConfig file usage
    • Namespace specification
    • Custom client configuration
  3. Configuration Access (main.go):

    • Configuration availability check
    • Bulk configuration retrieval
    • Single value access
    • Error handling

Notes

  • The example supports both in-pod and out-of-pod deployments
  • In-pod deployment uses the pod's service account
  • Out-of-pod deployment requires KubeConfig file
  • ConfigMap changes are automatically reflected
  • Proper RBAC permissions are required
  • Configuration paths can be customized based on needs

Source: SKILL.md on GitHub

1 alert16d5 checks · Risk MEDIUM
  • Gen Agent Trust Hub16d

    The skill provides a comprehensive development guide and code examples for the GoFrame v2 framework. While highly informative for Go developers, it contains several examples with hardcoded placeholder secrets, tokens, and specific local file paths to sensitive configuration files (like Kubernetes credentials). These elements are provided for demonstration purposes but represent insecure practices if used in production without modification.

  • Socket16d

    5 alerts: gptSecurity, gptAnomaly

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    227/949 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 911705d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 months ago.

Steadyupdated 4 months ago
  • Go
  • Database
  • goframe
  • orm
  • http
  • grpc
  • microservices
  • crud
  • scaffolding
  • middleware

README badge

README badge for gogf/skills

Provides instruction and conventions for developing with GoFrame v2, a modular Go framework for building HTTP and gRPC services, microservices, and database operations using its ORM, CLI tooling, and project scaffolding. Use this skill when the target project has GoFrame v2 as a dependency or when the user requests scaffolding, migrations, or service development with GoFrame conventions.

Generated from the current SKILL.md.

When should I use this skill?
Use this skill only when your Go project uses GoFrame v2, indicated by github.com/gogf/gf/v2 in go.mod or imports. Do not use for generic Go projects, frontend work, or infrastructure tasks unrelated to GoFrame.
Should I manually set created_at and updated_at fields?
No. GoFrame automatically writes created_at on insert and updated_at on insert/update/save. Manually setting these fields is redundant and violates project conventions.
What should I use for database operations instead of g.Map?
Always use DO objects from internal/model/do/. DO struct fields are interface{}, unset fields remain nil and are automatically ignored by the ORM.
How does soft delete work in GoFrame?
Call Delete() on the DAO; GoFrame automatically converts it to UPDATE SET deleted_at = NOW(). Queries automatically filter out soft-deleted rows without requiring manual WhereNull conditions.
Where should I implement business logic?
Implement business logic directly in the service/ directory. Do not use the logic/ directory unless explicitly requested.

Generated from the current SKILL.md. These answers refresh after source changes.