Modify 'is_default' behavior relative to 'is_protected' for templates
With the addition of the general is_protected flag on all objects,
the is_default flag on cluster and node group templates is semi-redundant.
Its semantics should be changed; specifically, gating of update and
delete operations should be handled exclusively by is_protected. The
is_default flag should still be used to identify default templates for bulk
update and delete operations by the sahara-templates tool.
Blueprint information
- Status:
- Complete
- Approver:
- Trevor McKay
- Priority:
- Medium
- Drafter:
- Trevor McKay
- Direction:
- Approved
- Assignee:
- Trevor McKay
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-3
- Started by
- Trevor McKay
- Completed by
- Trevor McKay
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Replace 'is_default' with 'is_protected' for templates
Addressed by: https:/
Remove overlap of 'is_default' and 'is_protected' for templates
Addressed by: https:/
Change 'ignore_default' to 'ignore_
Addressed by: https:/
Add 'is_protected' field to all default templates
