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.