How stack-spot/stackspot-workflows-action works
Main Components
a) Core Components:
• Setup Action Module
• Repository Creation Actions
• Provider-specific Implementations
• Workflow Templates
• Helper Services
b) External Integration Points:
• SCM Providers (GitHub, GitLab, Azure DevOps, Bitbucket)
• StackSpot Workflow API
• StackSpot Portal
Component Relationships
Use the following connection types:
Specific Implementation Details
[Setup Action Module]
• Handles SCM setup
• Manages workflow configuration
• Processes hidden inputs
[Repository Creation Actions]
• Azure Implementation
• Bitbucket Implementation
• GitHub Implementation
• GitLab Implementation
[Provider Clients]
• Azure API Client
• Bitbucket API Client
• GitHub API Client
• GitLab API Client
[Helper Services]
• Git Helper
• HTTP Client
• STK Helper
• Utility Functions
Important Flows to Highlight
a) Repository Creation Flow:
StackSpot Portal -> Setup Action -> Provider Client -> SCM Provider
• > Write Context File -> Update Workflow Status
b) Workflow Template Management:
Provider-specific Templates -> Workflow Setup -> SCM Integration
Implementation Notes
• The modular nature of the provider implementations
• The separation of concerns between setup and creation actions
• The common helper services shared across providers
• The workflow template structure for each provider