Is your feature request related to a problem? Please describe.
To create an Azure Archive Location resource it is requiring the use of the Rubrik-internal cloud_account_id string. This is something used on the back-end of Rubrik to uniquely track the Subscription that has been onboarded, but is not referenceable in a TF plan unless the archive location and subscription onboarding modules are executed in the same plan. Customers looking to factor their deployments with these two plans operating separately are unable to do so easily without first looking up the ID in another way.
Describe the solution you'd like
Provide a data source for the Azure Subscription that would allow the TF plan to reference details about the Rubrik Cloud Account representation of the Subscription. This would enable the archive location code to easily reference the cloud_account_id value and solve the problem described above.
Describe alternatives you've considered
The only workaround is to locate the ID another way and provide it statically in the TF plan used to create the archive locations.
Is your feature request related to a problem? Please describe.
To create an Azure Archive Location resource it is requiring the use of the Rubrik-internal
cloud_account_idstring. This is something used on the back-end of Rubrik to uniquely track the Subscription that has been onboarded, but is not referenceable in a TF plan unless the archive location and subscription onboarding modules are executed in the same plan. Customers looking to factor their deployments with these two plans operating separately are unable to do so easily without first looking up the ID in another way.Describe the solution you'd like
Provide a data source for the Azure Subscription that would allow the TF plan to reference details about the Rubrik Cloud Account representation of the Subscription. This would enable the archive location code to easily reference the
cloud_account_idvalue and solve the problem described above.Describe alternatives you've considered
The only workaround is to locate the ID another way and provide it statically in the TF plan used to create the archive locations.
Additional context
.