@@ -174,6 +174,14 @@ ServiceMappings file. Add the `ResourceConfig` for your resource:
174
174
similar resources, and the comments in
175
175
[pkg/apis/core/v1alpha1/servicemapping_types.go](pkg/apis/core/v1alpha1/servicemapping_types.go).
176
176
177
+ 1. If you are adding a resource that is already supported in v1alpha1, specify
178
+ the following fields
179
+ ([example](https://github.com/GoogleCloudPlatform/k8s-config-connector/blob/8ba13a0c1e0563e0e6f9a9f6eeb8a693f9c73acf/config/servicemappings/certificatemanager.yaml#L30-L31)):
180
+ 1. Set `v1alpha1ToV1beta1` to `true`.
181
+ 1. Set `storageVersion` to `v1alpha1`.
182
+
183
+ 1. Ensure the `autoGenerated` field is unset.
184
+
177
185
1. Add `resourceID` if the resource has the resource ID. The value of
178
186
` targetField` should be the field name of the user-specified resource ID
179
187
field (value of `metadataMapping.name`) or the field name of the
@@ -236,14 +244,6 @@ ServiceMappings file. Add the `ResourceConfig` for your resource:
236
244
237
245
1. Fill out the `resourceAvailableInAssetInventory`. Set to false.
238
246
239
- 1. If you are adding a resource that is already supported in v1alpha1, specify
240
- the following fields
241
- ([example](https://github.com/GoogleCloudPlatform/k8s-config-connector/blob/8ba13a0c1e0563e0e6f9a9f6eeb8a693f9c73acf/config/servicemappings/certificatemanager.yaml#L30-L31)):
242
- 1. Set `v1alpha1ToV1beta1` to `true`.
243
- 1. Set `storageVersion` to `v1alpha1`.
244
-
245
- 1. Ensure the `autoGenerated` field is unset.
246
-
247
247
1. Add `hierarchicalReferences` if they exist. Determine if the corresonding
248
248
Terraform resource exposes one or more parent resources through top-level
249
249
fields. These fields can have names like `org_id`, `parent_org_id`,
0 commit comments