build-features-and-cloud-api

Transform approved cloud analysis documents into executable behavioral test stacks for AWS, Azure, and GCP deployments.

85|80|Updated Jul 26, 2023
One-click install
npx skills add https://github.com/finos/common-cloud-controls --skill build-features-and-cloud-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-features-and-cloud-api
Source: https://github.com/finos/common-cloud-controls/tree/main/skills/build-features-and-cloud-api
Command: npx skills add https://github.com/finos/common-cloud-controls --skill build-features-and-cloud-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of assembling disjointed artifacts into a runnable behavioural test stack for cloud services, ensuring alignment with approved analysis and FINOS Common Cloud Controls compliance standards.

Core Features & Use Cases

  • End-to-end test stack generation: Transforms an approved analysis document for a cloud service into all required artifacts for runnable behavioural tests, including Gherkin feature files, cross-cloud Go cloud-api implementations, modular terraform integration fixtures, and Privateer YAML configurations.
  • Cross-cloud compatibility: Supports AWS, Azure, and GCP providers, with factory registration and service type registry updates for new or extended cloud service IDs.
  • Compliance-aligned guardrails: Includes built-in honesty rules for non-testable scenarios, minimal cost terraform resource guidelines, and explicit scope boundaries to avoid overprovisioning.
  • Use Case: A cloud compliance engineer adding behavioural tests for a new virtual-machines service can use this Skill to automatically generate all required test code, infrastructure, and CI configurations from their approved analysis, reducing implementation time from weeks to hours.

Quick Start

Use the build-features-and-cloud-api skill to turn your approved cloud service analysis document into a complete, runnable behavioural test stack including Gherkin features, cloud-api code, terraform fixtures, and Privateer configurations.

Frequently Asked Questions about build-features-and-cloud-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Gherkin feature files and cloud-api packages from a cloud compliance analysis document?

To generate Gherkin feature files and Go cloud-api packages, an approved cloud service behavioural test analysis document is transformed into a complete, runnable end-to-end test stack including infrastructure fixtures and configurations.

Can I use Privateer configurations to run behavioural tests across AWS, Azure, and GCP?

Yes, Privateer YAML configurations support running behavioural tests across AWS, Azure, and GCP by utilizing cross-cloud Go cloud-api packages and modular terraform integration fixtures aligned with FINOS Common Cloud Controls.

What is the best way to automate cloud compliance test stack creation for FINOS Common Cloud Controls?

The best way to automate cloud compliance test stack creation is transforming approved analysis documents into Gherkin features, cloud-api code, terraform fixtures, and Privateer configurations aligned with FINOS Common Cloud Controls catalogs.

Do I need an approved analysis document before implementing terraform integration fixtures for cloud services?

Yes, an approved cloud service behavioural test analysis document is required to ensure the generated terraform integration fixtures, Gherkin features, and Privateer configurations align with compliance standards and avoid overprovisioning resources.

How does behavioural test infrastructure handle non-testable compliance scenarios in regulated public cloud deployments?

Behavioural test infrastructure handles non-testable compliance scenarios using built-in honesty rules that explicitly define scope boundaries, ensuring only testable scenarios generate code while adhering to minimal cost terraform resource guidelines.

Does this approach support adding new cloud service IDs with factory registration for cross-cloud providers?

Yes, implementing the test stack includes factory registration and service type registry updates for new or extended cloud service IDs, ensuring cross-cloud compatibility across AWS, Azure, and GCP providers.