epam / epam/hub-extensions

`hubctl stack init <statefile>` command does not recover certain env parameters from state

Open
#72 0 comments 0 reactions 1 assignee Claimed by @akranga View on GitHub
bug help wanted
Dominant language
Shell
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Steps to reproduce:
1. Create a stack template with one or few parameters defined with a `component` discriminator, for example:

```
- name: ingress
component: mlflow
parameters:
- name: hosts
fromEnv: MY_COOL_ENV_VAR
```
2. Init, configure, and deploy the stack.
3. Verify that `MY_COOL_ENV_VAR` value is present in the `.env` file
4. Re-initialize the `stack` from `state`: `hubctl stack init `
5. `MY_COOL_ENV_VAR` is not present in the `.env` file and a user is asked to enter it again on `hubctl stack configure`

Expected:
`MY_COOL_ENV_VAR` should be present in the `.env` file.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.