Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Design better format for solutions.yaml #1582

Closed
sayf-eddine-scality opened this issue Aug 28, 2019 · 0 comments
Closed

Design better format for solutions.yaml #1582

sayf-eddine-scality opened this issue Aug 28, 2019 · 0 comments
Labels
complexity:easy Something that requires less than a day to fix kind:debt Technical debt topic:solutions Anything related to external "Solutions" integration with the platform

Comments

@sayf-eddine-scality
Copy link
Contributor

Component:
solutions, salt

Why this is needed:
we need to version-ize solutions.yaml and design a format for it
What should be done:

Implementation proposal (strongly recommended):

Test plan:
@sayf-eddine-scality sayf-eddine-scality added moonshot topic:solutions Anything related to external "Solutions" integration with the platform complexity:easy Something that requires less than a day to fix labels Aug 28, 2019
@sayf-eddine-scality sayf-eddine-scality mentioned this issue Aug 28, 2019
Merged
@nootal nootal added the kind:debt Technical debt label Sep 4, 2019
gdemonet added a commit that referenced this issue Oct 14, 2019
@gdemonet
salt/solutions: Revamp configuration file
df40353 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
gdemonet added a commit that referenced this issue Oct 14, 2019
@gdemonet
salt/solutions: Revamp configuration file
95fa39e 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
@gdemonet gdemonet mentioned this issue Oct 14, 2019
Closed
10 tasks
gdemonet added a commit that referenced this issue Oct 14, 2019
@gdemonet
salt/solutions: Revamp configuration file
18a2ac0 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
gdemonet added a commit that referenced this issue Oct 17, 2019
@gdemonet
salt/solutions: Revamp configuration file
1f9a58f 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
gdemonet added a commit that referenced this issue Oct 21, 2019
@gdemonet
salt/solutions: Revamp configuration file
4d1fb1b 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
gdemonet added a commit that referenced this issue Oct 22, 2019
@gdemonet
salt/solutions: Revamp configuration file
cb21e3a 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
gdemonet added a commit that referenced this issue Nov 7, 2019
@gdemonet
salt/solutions: Revamp configuration file
dfda8d5 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
gdemonet added a commit that referenced this issue Nov 15, 2019
@gdemonet
salt/solutions: Revamp configuration file
df113e0 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
alexandre-allard pushed a commit that referenced this issue Feb 12, 2020
@gdemonet @alexandre-allard
salt/solutions: Revamp configuration file
a15fea3 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
TeddyAndrieux pushed a commit that referenced this issue Feb 12, 2020
@gdemonet @TeddyAndrieux
salt/solutions: Revamp configuration file
750a797 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
TeddyAndrieux pushed a commit that referenced this issue Feb 13, 2020
@gdemonet @TeddyAndrieux
salt/solutions: Revamp configuration file
0019ecc 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
TeddyAndrieux pushed a commit that referenced this issue Feb 24, 2020
@gdemonet @TeddyAndrieux
salt/solutions: Revamp configuration file
542cf10 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
TeddyAndrieux pushed a commit that referenced this issue Feb 25, 2020
@gdemonet @TeddyAndrieux
salt/solutions: Revamp configuration file
382e3d7 
A new field, currently named `active` (may be a poor choice, we'll see
with first user interactions, `activeVersions` could be more explicit),
is introduced to set which version of a Solution should be used for the
cluster-wide components of this Solution (i.e. the Admin UI and CRDs for
now).
Validation of the file format is added, using the usual `kind` and
`apiVersion` fields. Later improvements could use some OpenAPI schema.

Fixes: #1582
@bert-e bert-e closed this as completed in 88dfbfa Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
complexity:easy Something that requires less than a day to fix kind:debt Technical debt topic:solutions Anything related to external "Solutions" integration with the platform
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rewrite Solutions management scality/metalk8s
3 participants
@nootal @sayf-eddine-scality @gdemonet