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
All topology elements now contain an instance_configuration_version field. We should add this field to the schema. Also, it is now possible to use different instance_configuration_ids from the ones defined in the deployment template. So, we should make the necessary changes so that it's possible to set the instance_configuration_id for all resources.
Testing
We should test the following:
The instance_configuration_id and instance_configuration_version fields can be read and updated for all resources.
It's possible to use an instance_configuration_id different from the one in the template.
Context
We currently can't specify an instance_configuration_version, which forces us to use the instance_configuration_versions defined in the template. The same goes for the instance_configuration_id, which currently can't be different from the ones in the template, which blocks us from using different hardware types for specific resources/ES tiers.
The text was updated successfully, but these errors were encountered:
Overview
All topology elements now contain an
instance_configuration_version
field. We should add this field to the schema. Also, it is now possible to use differentinstance_configuration_id
s from the ones defined in the deployment template. So, we should make the necessary changes so that it's possible to set theinstance_configuration_id
for all resources.Testing
We should test the following:
instance_configuration_id
andinstance_configuration_version
fields can be read and updated for all resources.instance_configuration_id
different from the one in the template.Context
We currently can't specify an
instance_configuration_version
, which forces us to use theinstance_configuration_version
s defined in the template. The same goes for theinstance_configuration_id
, which currently can't be different from the ones in the template, which blocks us from using different hardware types for specific resources/ES tiers.The text was updated successfully, but these errors were encountered: