Hello,
/kind compatibility
What happened:
In CPO 1.35.x a new field called ShareAccessIDs was introduced. According to the docs this field is required and the ShareAccessID is deprecated and optional. However the log based on the issue reported by one user in velero-plugin-for-openstack says they are mutually inclusive:
invalid volume context: parameter 'shareAccessID' forbids 'shareAccessIDs' to be set
What you expected to happen:
My question is whether the 2 fields could be reconfigured to be set at the same time and code would prefer the new one? This would ensure users can configure both of them and retire the old one when it's abandoned.
If not the the users/consumers have to set proper parameter based on the CPO version, which is not natural (e.g. Velero plugin to look for manila container and check which image version is used).
How to reproduce it:
Set both shareAccessID and shareAccessIDs fields at the same time.
Anything else we need to know?:
No, thank you for looking into this.
Environment:
- openstack-cloud-controller-manager(or other related binary) version: 1.35.x
- OpenStack version: x
- Others: x
Hello,
/kind compatibility
What happened:
In CPO 1.35.x a new field called
ShareAccessIDswas introduced. According to the docs this field is required and theShareAccessIDis deprecated and optional. However the log based on the issue reported by one user in velero-plugin-for-openstack says they are mutually inclusive:What you expected to happen:
My question is whether the 2 fields could be reconfigured to be set at the same time and code would prefer the new one? This would ensure users can configure both of them and retire the old one when it's abandoned.
If not the the users/consumers have to set proper parameter based on the CPO version, which is not natural (e.g. Velero plugin to look for manila container and check which image version is used).
How to reproduce it:
Set both
shareAccessIDandshareAccessIDsfields at the same time.Anything else we need to know?:
No, thank you for looking into this.
Environment: