-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[develop] salt.modules.at was hopelessly broken on Solaris-like platforms #36873
Conversation
Is it acceptable to do a 2nd PR to clean up salt.modules.at and use the jenkins pipeline for testing? |
Unfortunately salt.states.at is still broken, will fix this to use at.* in all cases. |
salt.states.at was actually pretty horrible :(
Changes to the return of the state were unavoidable. If tests break I will fix after jenkins run. |
Updated the checks for the at state, now mock data is injected for the at.at, at.jobcheck, at.atrm module functions. The result was also updated to reflect the new result data. |
Thank you very much @sjorge for this. Looks great! |
* upstream/develop: [develop] salt.modules.at was hopelessly broken on Solaris-like platforms (saltstack#36873) Fix saltstack#36461, AttributeError because of .lower() (saltstack#36462) Add versionadded tag for new create_datacenter function (saltstack#36905) [fix] pkg.installed call on pkg.install (saltstack#36904) Create datacenter gh (saltstack#36826) Typos are not fun! (saltstack#36901) Add full SSE demo (saltstack#36878) Update tutorial.rst (saltstack#36892)
What does this PR do?
salt.modules.at_solaris is compatible in output with salt.modules.at
Some cleanup happened along the way, that could probably also happen to salt.modules.at
What issues does this PR fix or reference?
N/A
Previous Behavior
All at.* calls would raise exceptions on Solaris-like platforms.
New Behavior
All at.* calls now work fine on Solaris-like platforms (tested on Solaris 10, OmniOS and SmartOS)
Although the Solaris 10 box got minimal testing, it was a prod box from work down for maintenance -- why I could test in the first place.
Tests written?
Yes