Configuration option to include/exclude resource registration

Registered by Vijendar Komalla

Currently when heat engine starts, all the in-tree resources get registered by default.
There should be an option to exclude some resource registration. For example, some cloud provider might not want to expose some cloud resources through heat orchestration.
(Please ignore/close this blueprint if this does not look like a valid scenario)

Blueprint information

Status:
Complete
Approver:
Angus Salkeld
Priority:
Medium
Drafter:
Angus Salkeld
Direction:
Needs approval
Assignee:
Angus Salkeld
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Angus Salkeld
Completed by
Angus Salkeld

Related branches

Sprints

Whiteboard

I think this can be quite easily done in the global environment (etc/heat/environment.d/z_last_file.yaml).

  resource_registry:
    'AWS::*':

At least, I'll try that out.

Gerrit topic: https://review.openstack.org/#q,topic:bp/exclude-resources-option,n,z

Addressed by: https://review.openstack.org/52803
    Add support to disable resources

Addressed by: https://review.openstack.org/53261
    Prove that a user can't remove global resources

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.