cloudtools/stacker

Package sources and conflicting file names for raw templates

Open

#667 opened on Oct 10, 2018

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Python (706 stars) (166 forks)batch import
enhancementhelp wanted

Description

In the following scenario you would end up with two VPC stacks. Is there way to force a certain raw package to be used when defining template_path?

package_sources:
  git:
    - uri: git@github.com:SomeUser/vpc.git
    - uri: git@github.com:SomeUser/config.git

stacks:
  - name: vpc
    template_path: cloudformation.yaml
  - name: config
    template_path: cloudformation.yaml

Contributor guide

Tech stack
pythonaws
Domain
infrastructure
Issue type
feature
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
PythonCloudFormationstacker configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how stacker resolves template path from git based package sources. Look at the configuration parsing in `stacker/config.py` and the blueprint loading in `stacker/blueprints.py`. The issue suggests adding a way to specify which package to use when two packages provide the same filename. A possible approach is to allow a package identifier (e.g., URI) in the stack definition. Check existing comments on the issue for any proposed solutions.