You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently x-terraform-id and x-terraform-status-field extensions are defined on a property level; however this means that there's potential that multiple properties could be set with these extensions enabled.
Describe the solution you'd like
To avoid this issue, a better design would be to move the properties one level up along with the schema definitions root properties and if defined the corresponding value will define the expected id or status field to use; otherwise default value will fall to normal behaviour which is expect to have a property named 'id' and 'status' (for asynchronous operations)
What's required to consider this feature request complete?
If the property is defined in the root level, the value should define the expected property to use. In the case of 'x-terraform-id' the value set will be used to identify the id of the resource and accordingly the value set for x-terraform-status-field will be used as status field.
If the properties are not present in the root level, then default names will be used instead. These being 'id' and 'status' by default.
If non of the above are met, an error should be throw upon validation
Checklist
Don't forget to go through the checklist to make sure the issue is created properly:
I have added a corresponding label (feature request/bug/etc) to the issue (right side menu)
I have added this issue to the 'API Terraform Provider' GitHub project (right side menu)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Currently x-terraform-id and x-terraform-status-field extensions are defined on a property level; however this means that there's potential that multiple properties could be set with these extensions enabled.
Describe the solution you'd like
To avoid this issue, a better design would be to move the properties one level up along with the schema definitions root properties and if defined the corresponding value will define the expected id or status field to use; otherwise default value will fall to normal behaviour which is expect to have a property named 'id' and 'status' (for asynchronous operations)
Acceptance criteria
What's required to consider this feature request complete?
Checklist
Don't forget to go through the checklist to make sure the issue is created properly:
The text was updated successfully, but these errors were encountered: