rafaeltuelho

description	argument-hint
Index GitHub repos with Augment Context Connectors and generate MCP server config	org/repo1#main, org/repo2#develop, org/repo3#v1.0

You are setting up Augment Context Connectors to index multiple GitHub repositories and configure an MCP server for cross-repo semantic search.

Step 1: Gather User Input

If $ARGUMENTS is empty or not provided, ask the user for:

rafaeltuelho

type	description
agent_requested	/run AI Tutor

AI Tutor Mode

Welcome! I'm your interactive guide to Augment Code. I'll help you accomplish your tasks while teaching you the most effective Augment features to use along the way.

How This Works

rafaeltuelho

type	description
agent_requested	/run plan mode

Plan Mode Rules

Quick Start: Ask Questions First

When entering Plan Mode, IMMEDIATELY ask focused questions to gather critical information:

rafaeltuelho

General agent guidelines

Response Formatting

• Whenever listing or mentioning a file path in the response, MAKE IT a clickable link so I can click it and open it in the Editor.

External frameworks and libraries documentation

• Whenever possible, try to leverage the Context 7 MCP tools to retrieve updated libraries, frameworks, and SDK docs
• Try to retrieve documentation thatis relevant and aligned to the version being used by the project (referenced in the package management)

Explainability

• Always list the tools called (if any) during the prompt processing at the end of your response.

rafaeltuelho

apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: trivy-image-scan
  annotations:
    task.results.format: application/json
    task.results.type: roxctl-image-scan
    task.results.key: SCAN_OUTPUT
    task.output.location: logs
    task.results.container: step-report

rafaeltuelho

Dynamic Plugin export for Red Hat Developer Hub based iDPs

This tutorial describes how to export a existing Backstage plugin as a Dynamic plugin to be loaded into Red Hat Developer Hub.

For this demo I choose the Announcements plugin for Backstage as it is composed by multiple components including front-end UI, backend and search-backend.

Reference documentation:

• Official guide from the product documentation
• A simple getting started project for building Dynamic Plugins with Red Hat Developer Hub

rafaeltuelho

schemaVersion: 2.2.0
metadata:
  generateName: secured-app
components:
  - volume:
      size: 4Gi
    name: home
  - name: development-tooling
    container:
      image: quay.io/devfile/universal-developer-image:latest

rafaeltuelho

apiVersion: charts.helm.k8s.io/v1
kind: OpenshiftArtifactoryHa
metadata:
  name: openshiftartifactoryha
  namespace: artifactory
spec:
  artifactory-ha:
    artifactory:
      joinKey: ae576b44d1dfe2ef3750cfbf.... #openssl rand -hex 32
      masterKey: 4c2bd4d2082a0c2fa2e54... #openssl rand -hex 32

rafaeltuelho

global:
  postgresql:
    auth:
      postgresPassword: "secret"
      username: "artifactory"
      password: "artifactory"
      database: "artifactory"
primary:
  persistence:
    enabled: false

rafaeltuelho

# Default values for artifactory-oss.
# This is a YAML-formatted file.

# Beware when changing values here. You should know what you are doing!
# Access the values with {{ .Values.key.subkey }}

# This chart is based on the main artifactory chart with some customizations.
# See all supported configuration keys in https://github.com/jfrog/charts/tree/master/stable/artifactory

containerSecurityContext: