-
Notifications
You must be signed in to change notification settings - Fork 161
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
idrac_server_config_profile improvement requested (request) #137
Comments
@ThierryBesancon, thank you for submitting this feature request. While the team will triage this and add to our internal backlog for appropriate prioritization, in the meanwhile, I can think of the following workaround to achieve your workflow:
|
Hello Thanks for your workaround but as i use a NFS share, Thierry |
@ThierryBesancon, I agree that this becomes a little cumbersome when working with CIFS or NFS shares. |
@ThierryBesancon We have added this feature with the latest commit, where "scp_file" option can be used to specify custom file name. Kindly verify and let us know |
@ThierryBesancon This feature has been added with the latest commit. Hence closing issue. Thank you for the good suggestion |
Hello
When you export the server config profile with
idrac_server_config_profile
, you can not specify the destination file. You can provide ascp_file
definition but it is silently ignored. When you readidrac_server_config_profile.py
, you clearly see the parameter is ignored and the profile is always namedipaddr_YYYYmmdd_HHMMSS
( extension.xml
or.json
). That makes the name quite unpredictable (especially as python ansible is quite slow). Image i want to export the scp as XML, do some xml trickery on it and then push it back with an import. Exporting to an unpredictable name makes like harder in ansible... (unless you have a magic trick to do that that you can share with us?)So my request is: would it be possible for
idrac_server_config_profile
to export toipadd_YYYYmmdd_HHMMSS
by default (to stay compatible with previous releases) but honourscp_file
when set? If the request is refused, please update the documentation not to be misleading as it is presently: specify thatscp_file
is only used forimport
and never forexport
.Thanks in advance for your future comment on my request.
The text was updated successfully, but these errors were encountered: