Hi Praveen,
The docs you referred to in the plugin guide is for the resource property attributes - they have nothing to do with parameters. This is an important distinction because there is also an "immutable" parameter attribute. The "immutable" property attribute was added because an equivalent to AWS' "Updates are not supported" functionality was needed: https://specs.openstack.org/openstack/heat-specs/specs/juno/implement-aws-updates-not-supported.html#aws-cloudformation Jason ________________________________ From: Praveen Yalagandula <yprav...@avinetworks.com> Sent: Monday, May 2, 2016 11:55 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [heat] update_allowed vs. immutable What is the difference between "update_allowed" and "immutable" parameters for a property? According to the plugin guide at http://docs.openstack.org/developer/heat/developing_guides/pluginguide.html: update_allowed: True if an existing resource can be updated, False means update is accomplished by delete and re-create. Default is False. immutable: True means updates are not supported, resource update will fail on every change of this property. False otherwise. Default is False. Since any resource can be deleted and then re-created, it seems "update_allowed" is the right parameter to define. Why do we need "immutable"? Thanks, Praveen Yalagandula Avi Networks
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
