Skip to content

Comments

feat: Add AWS CodePipeline Get Pipeline Execution component#3225

Merged
forestileao merged 4 commits intosuperplanehq:mainfrom
manasa-bhagwat:feat/2753-get-pipeline-execution
Feb 23, 2026
Merged

feat: Add AWS CodePipeline Get Pipeline Execution component#3225
forestileao merged 4 commits intosuperplanehq:mainfrom
manasa-bhagwat:feat/2753-get-pipeline-execution

Conversation

@manasa-bhagwat
Copy link
Contributor

@manasa-bhagwat manasa-bhagwat commented Feb 23, 2026

Implements #2753

This PR adds the aws.codepipeline.getPipelineExecution component, which retrieves the status and details of a specific AWS CodePipeline execution using the GetPipelineExecution API.

What

The component returns the full execution details including status, status summary, trigger info, artifact revisions, execution mode/type, pipeline name, and pipeline version. It is a simple synchronous one-shot read — no polling, no EventBridge, no cancel. The Execution ID field supports expressions, enabling dynamic wiring from a preceding Run Pipeline component.

Backend

  • pkg/integrations/aws/codepipeline/get_pipeline_execution.go — component (all core.Component methods)
  • pkg/integrations/aws/codepipeline/client.goGetPipelineExecutionDetails() method, GetPipelineExecutionDetailsResponse struct (existing typed GetPipelineExecution() used by RunPipeline is untouched)
  • pkg/integrations/aws/codepipeline/get_pipeline_execution_test.go — Setup + Execute tests
  • pkg/integrations/aws/codepipeline/example_output_get_pipeline_execution.json — example output
  • pkg/integrations/aws/codepipeline/example.goExampleOutput() wiring
  • pkg/integrations/aws/aws.go — registered in Components()

Frontend

  • web_src/src/pages/workflowv2/mappers/aws/codepipeline/get_pipeline_execution.ts — canvas mapper
  • web_src/src/pages/workflowv2/mappers/aws/index.ts — registered mapper + state registry

Docs

  • docs/components/AWS.mdx — generated with make gen.components.docs

Tests

  • Setup: invalid config, missing region, missing pipeline, missing executionId, valid config
  • Execute: invalid config, missing credentials, valid request emits pipeline execution details

Demo

Get.Pipeline.Execution.-.Demo.SuperPlane.mp4

Signed-off-by: manasa <manasa.bhagwat.work@gmail.com>
Signed-off-by: manasa <manasa.bhagwat.work@gmail.com>
…cution

Signed-off-by: manasa <manasa.bhagwat.work@gmail.com>
@manasa-bhagwat manasa-bhagwat marked this pull request as ready for review February 23, 2026 12:04
@manasa-bhagwat
Copy link
Contributor Author

Hi @forestileao

This is pr ready for review when you get a chance.

Adds the getPipelineExecution component.

@lucaspin lucaspin requested a review from forestileao February 23, 2026 12:17
@forestileao forestileao self-assigned this Feb 23, 2026
@forestileao
Copy link
Collaborator

@manasa-bhagwat You will need to fix the conflicts due to the merge of #3220

@manasa-bhagwat
Copy link
Contributor Author

@manasa-bhagwat I can do it for you actually :)

Thanks @forestileao!

Resolved the conflicts myself.
Should be good to go now.

@forestileao forestileao merged commit ab84976 into superplanehq:main Feb 23, 2026
3 checks passed
@forestileao
Copy link
Collaborator

@manasa-bhagwat Thanks again! The PR is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants