'integration' 검색 결과

Use this skill to select the right Salesforce integration pattern — from point-to-point to event-driven to hub-and-spoke — by applying the official Salesforce two-axis decision framework (integration type × timing) to a business integration scenario. Trigger keywords: integration pattern decision, choose integration approach, Salesforce integration architecture, when to use platform events vs API, integration type selection. NOT for implementation of any specific integration pattern (use domain-specific integration skills), MuleSoft architecture (use architect/mulesoft-anypoint-architecture), or middleware vendor selection. More triggers: integration decision record, Bulk API vs REST for a nightly load, external Id upsert, Named Credential vs Remote Site Setting, platform event vs CDC, who calls whom.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Operate FrontendIntegration resources from existing YAML definitions using kubectl, the Kubernetes command-line tool. Manage updates and enabled state, inspect build output, troubleshoot failures, and install or manage the frontend-forge extension.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a FrontendIntegration from existing YAML
• Update, enable, or disable a FrontendIntegration
• Inspect build output and troubleshoot failures

Generate FrontendIntegration YAML for frontend-forge from a simplified configuration containing one menu and one or more pages. Define resource tables or embedded iframe pages, with the bundled generator expanding menu placements into the required YAML structure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generating integration YAML for a CRD resource table
• Defining an embedded iframe page
• Converting a single-menu configuration into canonical YAML

Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, or eliminating anti-patterns such as Mockito-mocked HTTP clients or globally registered WireMock stubs. This should trigger for requests such as Review Java code for integration tests; Apply best practices for integration tests in Java code; Write Java integration tests with real infrastructure boundaries; Improve Testcontainers integration tests for Java code; Review integration test setup and teardown in Java projects. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code for Spring Boot integration tests; Apply best practices for Spring Boot integration tests in Java code; Write @SpringBootTest integration tests with Testcontainers; Configure dynamic properties for Spring integration tests; Review Spring Boot integration test profiles. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Research MCP connections, which let agents use external tools, and vendor integrations for Paperclip. Produce an evidence-backed planning pull request, obtain human approval for its exact revision, then implement and verify each approved connection separately.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Researching MCP and vendor connection requirements
• Preparing integration plans for human approval
• Implementing approved Paperclip connections separately

Analyzes one .NET project to plan integration tests for an Oracle-to-PostgreSQL migration. Identifies database access methods, prioritizes migration risks, and documents test cases, seed data, and coverage, including empty strings, NULL values, and timezone behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identifying database access methods that need integration tests
• Prioritizing tests for Oracle-specific behavior
• Planning checks for empty strings, NULL values, and timezones

Manage the credentials Arize uses to call LLM providers such as OpenAI and Anthropic. Create, inspect, update, or delete connections, configure allowed models and authentication methods, and retrieve connection IDs for use in evaluations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Connect an LLM provider to Arize
• Review existing connections and allowed models
• Rotate stored provider API keys

Use when you need to write or improve integration tests for Micronaut — @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode where appropriate, and Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT. This should trigger for requests such as Add Micronaut integration tests with Testcontainers; Wire dynamic datasource or broker URLs for @MicronautTest; Write @MicronautTest integration tests with Testcontainers; Configure replacement beans for Micronaut integration tests; Review Micronaut integration test lifecycle and resources. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when setting up or auditing a dedicated Salesforce integration user — Salesforce Integration user license, API-only profile, permission set layering, MFA waiver, and login monitoring. NOT for creating human users, roles, or login hours — use admin/user-management. NOT for login IP ranges, session lifetime, or OAuth client-credential hardening — use security/api-only-user-hardening. Trigger keywords: service account, API-only user, run-as user, client credentials execution user, LoginHistory, REQUEST_LIMIT_EXCEEDED, integration login failure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when managing Connected Apps for integration purposes — configuring OAuth policies, IP restrictions, refresh token expiry, pre-authorization assignment via profile or permission set, and monitoring connected app usage via EventLogFile. Also covers the running-integration operations: revoking a grant, rotating the consumer key or secret, pairing the app to an integration user's permission set, and the periodic review. Trigger keywords: 'revoke OAuth token', 'DeleteToken', 'OauthToken query returns nothing', 'ipRelaxation ENFORCE', 'permissionSetName', 'PermissionSetAssignment ExpirationDate', 'LoginHistory Application', 'connected app quarterly review', 'rotate consumer secret'. NOT for choosing which OAuth grant flow to implement — use integration/oauth-flows-and-connected-apps. NOT for decoding a specific OAuth error such as invalid_grant — use admin/connected-app-troubleshooting. NOT for authoring the full connectedApp / External Client App / Named Credential file or choosing the auth artefact — use admin/connected-apps-and-auth.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. Part of cursor-rules-java project

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Complete guide for ASP.NET Core Web API integration testing. Use when performing integration testing on Web API endpoints or validating ProblemDetails error format. Covers WebApplicationFactory, IExceptionHandler, Testcontainers multi-container orchestration, Flurl URL construction, and AwesomeAssertions HTTP validation. Keywords: webapi integration testing, WebApplicationFactory, asp.net core integration test, webapi integration test, IExceptionHandler, ProblemDetails, ValidationProblemDetails, AwesomeAssertions, Flurl, Respawn, Be201Created, Be400BadRequest, multi-container testing, Collection Fixture, global exception handling

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

기존 프로젝트의 구현 방식에 맞춰 외부 API 연동을 추가합니다. 설정, 인증, 오류 처리부터 등록과 테스트까지 기존 코드와 일관되게 구성합니다.

• 기존 프로젝트에 Jira 연동 추가
• 기존 방식에 맞는 Slack 연동 구현
• 연동 등록과 테스트 정비

Design, build, debug, and optimize connections to external APIs. The skill covers REST, GraphQL, event notifications through webhooks, authentication, retries, request limits, and logging to help produce integrations whose failures can be traced.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a new external API integration
• Building an API client with retries and authentication
• Investigating failed requests or missing results

Add DeepEval tracing to Python AI applications so execution steps appear in Confident AI. Choose a supported integration or manual @observe instrumentation, then capture inputs, outputs, step types, tags, and metadata.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trace execution steps in a Python AI application
• Select tracing integrations for an existing framework
• Add manual tracing with @observe

Find and call tools in connected services such as Linear and GitHub through superset mcp. This skill also helps diagnose connection and permission errors and access tools missing from an agent’s own tool list.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check which tools a connected service offers
• Create a Linear issue through a connected account
• Diagnose authentication and permission errors

Plan and review new Omnigent harness integrations, the adapters connecting agent runtimes to the platform. Compare SDK and subprocess approaches with native interface wrappers, using capability matrices and checklists for implementation and testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan a new agent runtime integration
• Compare SDK and native integration requirements
• Review approval, streaming, and session support

Choose Stripe APIs and payment interfaces for one-time payments, subscriptions, marketplaces, and financial accounts. Helps plan, modify, or review integrations, including connected account setup, payment method storage, and migration from deprecated APIs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose an API and interface for one-time payments
• Plan subscriptions and recurring billing
• Design connected accounts for a marketplace

Use when running integration tests in the VS Code repo. Covers scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows), their supported arguments for filtering, and the difference between node.js integration tests and extension host tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

INVOKE THIS SKILL when creating, reading, updating, or deleting Arize AI integrations. Covers listing integrations, creating integrations for any supported LLM provider (OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM, custom), updating credentials or metadata, and deleting integrations using the ax CLI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Complete guide for AutoFixture and Bogus integration. Use when you need to combine AutoFixture with Bogus to generate test data that is both anonymous and realistic. Covers SpecimenBuilder integration, hybrid generators, test data factories, and circular reference handling. Keywords: autofixture bogus integration, autofixture bogus, bogus integration, Faker, EmailSpecimenBuilder, PhoneSpecimenBuilder, NameSpecimenBuilder, realistic test data, semantic data, hybrid generator, HybridTestDataGenerator, OmitOnRecursionBehavior, circular reference

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add integration tests for a new syncable entity
• Test required fields, duplicates, and invalid references
• Verify successful creation, updates, and deletion