Jesus M. Rodriguez wrote:
Miroslav Suchý wrote:
According the code the the returned version is content of web.version
/etc/rhn/default/rhn_web.conf
I see as best option to create new config option web.apiversion which we
bump up independently on spacewalk version. And ideally return it back to
5.2 at least and act as API version 0.x never exist.
Yes maybe we can bump it to 100 or 10 to clearly state that it has nothing
to do with spacewalk versioning.
I'm ok with this, seems like using the web_version has caused some problems with
some scripts.
OK. Done as:
https://bugzilla.redhat.com/show_bug.cgi?id=472346
So to summarize what should happen,
1) add web.apiversion to /etc/rhn/default/rhn_web.conf
2) set the initial value to be 5.2
I set it to 10.0
At current it returns web.version + " Java"
http://tinyurl.com/5c2egq
I removed the Java suffix as we do no need it now to distinguish between
api.get_system_version and api.get_version. If this can be problem raise
your voice.
5) if you are relying on the value of api.get_system_version() please
switch the appropriate api.get_version() method.
Please now whenever you add new API call modify minor version
web.apiversion in web/conf/rhn_web.conf. And every Spacewalk release
bump up major version.
If you have better idea how to handle api versioning share the idea.
--
Miroslav Suchy
RHN Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
