Feature request: support multiple --mixin entries
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 65/100
Research direction
Start by locating the CLI option parsing for --mixin and the manifest-mixing path. Run the existing CLI tests before changing behavior; done means multiple --mixin options are accepted, applied one at a time, and later duplicate values override earlier ones.
Written by the indexing model from the issue text.
Description
Our team would like to use several sets of mixins, to provide more than one option in the manifest besides cluster. Currently it appears that when providing multiple --mixin options, only the last one is used.
For instance, some information is common for cluster, but some is dependent on Oracle database used (q1, q2, etc), and it would be nice to be able to say --mixin app.dev-fss.yaml --mixin app.q2.yaml - we sometimes also have different mode settings, like a set of dry-run/integration test settings, or a job that runs only specific steps in a process.
My proposal is that --mixin be altered to allow multiple options, where the merging happens one option at a time, so that the last mixin "wins" in case of duplicate structure. An alternate proposal might be to let the option be a colon-separated list of files.
Our alternatives to this feature request is to keep duplicating structure, to fundamentally reimplement this feature in preprocessing, and/or to keep using the deprecated handlebars syntax for as long as it remains.
- Dominant language
- Go
- Stars
- 2
- Forks
- 5
- Avg merge
- 3h 49m
- Merged PRs (30d)
- 34
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nais/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Maintainers usually reply within 1 day
-
mcp: mock schema is invalid GraphQL, so schema_* tests pass on a parse errorPossibly taken @Starefossen claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
mcp: schema_list_queries returns an array as structuredContent, and its outputSchema is invalidPossibly taken @Starefossen claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
evcc-io/evcc#35605 · 1 comment ·
Maintainers usually reply within 1 day
-
bug report
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nightgauge/nightgauge#2732 ·
Maintainers usually reply within 1 day
-
fix below CVEsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 5 days
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100