search

aws / aws-sdk-js-v3

Modularized AWS SDK for JavaScript.
Apache License 2.0
3.06k stars 573 forks source link

Volumes of FSx for NetApp ONTAP missing AdministrativeActions prop #6048

Closed RonyLevAri closed 4 months ago

RonyLevAri commented 5 months ago

Checkboxes for prior research

Describe the bug

According to the docs a volume entity should have an array of AdministrativeActions yet no such property is ever returned.
For example in UpdateVolumeCommand the volume entity is returned without such prop.

SDK version number

@aws-sdk/package-name@version, ...

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

node v21.2.0

Reproduction Steps

  1. create FSx ONTAP
  2. create volume
  3. update volume's tiering policy using the UpdateVolume command

Observed Behavior

returned volume response from update command missing AdministrativeActions

Expected Behavior

returned volume response from update command should have AdministrativeActions

Possible Solution

No response

Additional Information/Context

No response

aBurmeseDev commented 4 months ago

Hi @RonyLevAri - thanks for reaching out. I was able to reproduce this and confirm that AdministrativeActions is missing in the response. However, I can't say whether service API enforces it in the backend which is why I reached out to service team for further insights.

I'll circle back here once I hear back from service team. P128943399

aBurmeseDev commented 4 months ago

Service team responded:

AdministrativeActions is an optional field. Currently update-volume actions on FSx ONTAP volumes do not return any AdministrativeActions. But in the future they may be there. The update-volume action is shared across the various FSx engine types, so some of the other engines may return it.

Let me know if you have further question to service team.

github-actions[bot] commented 4 months ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.