focusaurus/hexagonal-lambda

APIG Deployment is created before other changes are done

Open

#3 opened on Sep 28, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (3 forks)github user discovery
bughelp wanted

Repository metrics

Stars
 (27 stars)
PR merge metrics
 (PR metrics pending)

Description

There's a terraform ordering problem where the forced deployment can be created while terraform is still making other changes to the API, so those changes are not included in the deployment snapshot. This can probably be hacked around with depends_on but that feels brittle to maintain. What I want is a way to force the deployment to always happen last (after all other APIG/lambda changes are complete).

Contributor guide

Research direction
Investigate Terraform resource dependencies and consider using the `depends on` meta argument or `create before destroy` lifecycle to ensure the deployment resource runs last.
Tech stack
javascript
Domain
devopscloudinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TerraformAWSGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65