cloudtools/stacker

Package sources and conflicting file names for raw templates

Open

#667 创建于 2018年10月10日

在 GitHub 查看
 (6 评论) (0 反应) (0 负责人)Python (706 star) (166 fork)batch import
enhancementhelp wanted

描述

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

贡献者指南

技术栈
pythonaws
领域
infrastructure
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
PythonCloudFormationstacker configuration
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
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.
Package sources and conflicting file names for raw templates · cloudtools/stacker#667 | Good First Issue