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.
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
Fixes #23352: Import/Export yaml with technique editor #5008
Fixes #23352: Import/Export yaml with technique editor #5008
Conversation
Commit modified |
1b69246
to
22b4e12
Compare
@@ -780,7 +816,7 @@ class TechniqueAPIService14( | |||
techniqueRevisions.getTechniqueRevision(name, version).map(_.map(JRRevisionInfo.fromRevisionInfo)) | |||
} | |||
|
|||
def getTechniqueWithData(techniqueName: TechniqueName, version: Option[TechniqueVersion]) = { | |||
def getTechniqueWithData(techniqueName: TechniqueName, version: Option[TechniqueVersion], format: String) = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
format should not be a string there
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Import seems to work as expected, but export does not. Once corrected and with the format change in a sealed trait/enum, you can self merge.
OK, actually export works too, elm just needed to be recompiled/reloaded. So just the format thing, and self merge! |
Commit modified |
22b4e12
to
fbf7f58
Compare
fbf7f58
to
2831d46
Compare
OK, merging this PR |
b59208e
into
Normation:branches/rudder/8.0
https://issues.rudder.io/issues/23352
Adds a new API to check whether a technique is valid or not (accepts a yaml, returns a json) to use to import a yaml technique
Modify getTechnique api to add a format parameter to return a yaml instead of a json to use to export a technique as yaml
modify the technique editor to use both new api/parameters