Correct typing for IOReadIOPSMax, IOWriteIOPSMax,... in systemd::manage_dropin #430
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
Using any of the following directives in
systemd::manage_dropin
orsystemd::manage_unit
resulted in a compilation error.IODeviceWeight
IOReadBandwidthMax
IOWriteBandwidthMax
IOReadIOPSMax
IOWriteIOPSMax
The types for these directives in
Systemd::Unit::Slice
andSystemd::Unit::Service
have now been updated.Example usage:
would result in a drop in file of:
This Pull Request (PR) fixes the following issues
Worth Noting
systemd::service_limit
uses for these parameters.systemd::service_limits
a wrapper tosystemd::manage_dropin
.it contains a translation for these parameters to maintain backwards compatibility.
systemd::service_limits
could then be deprecated.