Age | Commit message (Collapse) | Author | Files | Lines |
|
Now the generated app_helm_override_file and the list of
helm overrides is separate.
The former is to contain things like user provided overrides,
the latter is the list of absolute paths to preexisting helm value files.
The playbook joins all that into a final list of override files that is then
passed to helm.
Change-Id: I8b8ded38b39aa9a75e55fc63fa0e11b986556cb8
Issue-ID: OOM-1951
Signed-off-by: Michal Zegan <m.zegan@samsung.com>
|
|
In Dublin:
First project has taken ownership of own helm charts, oom repository must be obtained with subrepositories.
By default no applications are enabled, introducing a way to submit more override files in to installer
Issue-ID: OOM-1861
Signed-off-by: root <m.pilat@partner.samsung.com>
Change-Id: I1724de6b87bd0e9d17df4d0f55615a3f1c439d40
|
|
Change-Id: Ie0b4e812acf6fba4e4b8f082533ab2f998456095
Issue-ID: OOM-1877
Signed-off-by: Petr OspalĂ˝ <p.ospaly@partner.samsung.com>
|
|
Remove different phases for application role as
those are supposed to run after each other anyway
from playbook and pre/post steps can be disabled
by other means.
Enable Helm override file generation customization by
delegating it to separate role.
Separate Helm file transfer to own module.
NOTE: install.yml with all Helm commands (shell/command)
is not idempotent and should be fixed with separate
commit.
Issue-ID: OOM-1655
Change-Id: Ib29773c4d64a0529c71c3f93c2af7265ae94059f
Signed-off-by: Samuli Silvius <s.silvius@partner.samsung.com>
|