oxide_silo_idp_configuration: initial resource #442
Conversation
|
To implement this resource the proper way (e.g., read using provider ID) the API change referenced in oxidecomputer/omicron#8240 is required, which would make Release 15 required for this change. I'd like to ship this to be compatible with existing Oxide releases though so I'll update this resource to read using the provider name and silo ID and see if it works correctly. |
sudomateo
force-pushed
the
sudomateo/silo-idp-config
branch
from
3b66853 to
40ee907
Compare
There was a problem hiding this comment.
Thanks for starting the work on this!
I'd like to ship this to be compatible with existing Oxide releases though so I'll update this resource to read using the provider name and silo ID and see if it works correctly.
I'm not super keen on doing this TBH 🤔 The issue with referencing names instead of IDs is that they are all designed to be mutable. Even if they are not mutable today, it is in the design docs that all names should have the ability to be mutable at some point.
We'll be releasing R15 soon, and all of our customer's racks are still updated by us. So I don't think there should be much of a problem waiting for this feature a few weeks more right?
If we add the functionality to reference names, it will be much more problematic to remove it in the future.
I agree. I'll ask the customer who asked for this feature to see what their urgency and timelines are. I don't see why it can't wait for R15 especially since it'll be the better implementation. |
TODO