add data directory configuration component to advanced tab in rke2 create/edit cluster interface

[aalves08]

Summary

Fixes #10824

Occurred changes and/or fixed issues

• add data directory configuration component to advanced tab in rke2 create/edit cluster interface
• add unit test for data directory configuration component

Technical notes summary

• full manual test is dependent on [RFE] Option to provide data-dir for RKE2 provisioned by Rancher rancher#45038

Areas or cases that should be tested

• Go to RKE2 cluster creation interface and make sure the data configuration area is present on the Advanced tab of Cluster Configuration
• Make sure data persists and all works fine
• Make sure that cluster editing, the data configuration is disabled (not allowed to change the values)

Areas which could experience regressions

Screenshot/Video

NOTE: this video still doesn't cover the edit scenario properly, since we still don't have the changes needed on the backend to persist the data, but it proves the payload sent is correct

Screen.Recording.2024-05-16.at.12.28.21.mov

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[momesgin]

I think even though you are not allowed to change the values later, you should still be able to see the exact values you entered when you created the cluster. For example, I added separate paths for each of the three inputs when I created the cluster but this is what I see in edit mode:

[aalves08]

I think even though you are not allowed to change the values later, you should still be able to see the exact values you entered when you created the cluster. For example, I added separate paths for each of the three inputs when I created the cluster but this is what I see in edit mode:

That's because the backend part is still not done. The data doesn't persist yet. It's normal, for now 😬

But they payload is sent correctly. Check the RFC doc linked to the SURE issue where they show the agreed data struct.

[momesgin]

I think even though you are not allowed to change the values later, you should still be able to see the exact values you entered when you created the cluster. For example, I added separate paths for each of the three inputs when I created the cluster but this is what I see in edit mode:

That's because the backend part is still not done. The data doesn't persist yet. It's normal, for now 😬

But they payload is sent correctly. Check the RFC doc linked to the SURE issue where they show the agreed data struct.

now that makes sense! 😅

[aalves08]

I removed the optional chaining before (I agree it should not be needed) but this caused failures in at least another unit test... I just re-added them to move this forward :P

[momesgin]

I removed the optional chaining before (I agree it should not be needed) but this caused failures in at least another unit test... I just re-added them to move this forward :P

It seems you can fix all those failing tests by adding:

dataDirectories: {
   systemAgent:  '',
   provisioning: '',
   k8sDistro:    '',
}

to:

dashboard/shell/edit/provisioning.cattle.io.cluster/__tests__/utils/cluster.ts

Line 62 in b42c20e

},

[aalves08]

I removed the optional chaining before (I agree it should not be needed) but this caused failures in at least another unit test... I just re-added them to move this forward :P

It seems you can fix all those failing tests by adding:

dataDirectories: {
   systemAgent:  '',
   provisioning: '',
   k8sDistro:    '',
}

to:

dashboard/shell/edit/provisioning.cattle.io.cluster/__tests__/utils/cluster.ts

Line 62 in b42c20e

},

@momesgin code updated 🙏

[momesgin]

lgtm

[eva-vashkevich]

I am getting
"[Vue warn]: Invalid prop: type check failed for prop "value". Expected Object, got Undefined

found in

---> at shell/edit/provisioning.cattle.io.cluster/tabs/DirectoryConfig.vue
at shell/edit/provisioning.cattle.io.cluster/tabs/Advanced.vue
at shell/components/Tabbed/Tab.vue
at shell/components/Tabbed/index.vue
at shell/components/CruResource.vue
at shell/edit/provisioning.cattle.io.cluster/rke2.vue
at shell/components/CruResource.vue
at shell/edit/provisioning.cattle.io.cluster/index.vue
at shell/components/ResourceDetail/index.vue
at shell/pages/c/_cluster/_product/_resource/create.vue
<Shell/components/templates/default.vue> at shell/components/templates/default.vue

error thrown if I am trying to save rke2 cluster with default configuration.

Screen.Recording.2024-05-24.at.2.47.13.PM.mov

[aalves08]

Gm @eva-vashkevich . This was dependent on a backend issue rancher/rancher#45038 but all of the work has been merged, afaik. I am going to give this a test with a new backend image. Since I've done the frontend part without the backend being finished, I totally forgot to test it manually and merged this (all based on the RFC doc). 🙏

[aalves08]

Looking at the associated PRs, I don't think the backend part is completed to this date.... 🤔 The console message is not pretty, but I don't think there's a high risk with the current work merged. It allows for creating/edit of a cluster + the console message doesn't appear unless you're running the UI locally.

I've just pinged the backend team to get more information about the current status of their work and it's expected to be completed.

[eva-vashkevich]

@aalves08 Thank you for looking into it