Providers and status
Each AWS service and resource type requires a dedicated mapping to the five Jira Software Cloud data provider types – we are evolving this along the following lines:
Jira Software Cloud data providers
– feasibility has been verified, implementation is pending (CodeCommit)
– integration is pending
– integration is available, with additional AWS services in development
– feasibility has been verified, implementation is pending (App Config)
– integrations is blocked due to API not being sufficiently supported yet
AWS resource event mapping status
– dedicated support of applicable resource lifecycle events
– indirect support of applicable resource lifecycle events via CodePipeline
– support of result status reporting via CodePipeline (i.e. success/failure)
– integration feasibility has been verified but implementation is pending
– integration feasibility has not yet been verified
Providers and status
Each AWS service and resource type requires a dedicated mapping to the five Jira Software Cloud data provider types – we are evolving this along the following lines:
Jira Software Cloud data providers
SOURCE – feasibility has been verified, implementation is pending (CodeCommit)
BUILD – integration is pending
DEPLOYMENT – integration is available, with additional AWS services in development
FEATURE FLAG – feasibility has been verified, implementation is pending (App Config)
REMOTE LINKS (BETA) – integrations is blocked due to API not being sufficiently supported yet
AWS resource event mapping status
LIFECYCLE EVENTS – dedicated support of applicable resource lifecycle events
CODEPIPELINE EVENTS – indirect support of applicable resource lifecycle events via CodePipeline
CODEPIPELINE RESULT – support of result status reporting via CodePipeline (i.e. success/failure)
FUTURE – integration feasibility has been verified but implementation is pending
TRIAGE – integration feasibility has not yet been verified