'Next steps' after deployment

Registered by Steve McLellan

Something we'd like is the ability to present information to a user following deployment (as a link from the environments page, for instance). Once a user's deployed a set of services we'd like to give them information about what they can do with them.

For instance, given deployment of a database, we can give the user a connection string and links to information on the DB. For an environment containing a LAMP stack, we can give the user the IP address of the webserver as well as that database information.

A suggestion is to have this information in each application package with some placeholders; classes that can provide it (like database classes, webserver applications) should be able to provide some context specific information (IP address, connection string). As an initial step maybe this can just be text embedded in the manifest but ultimately it would be great to be able to refer to e.g. heat outputs.

Blueprint information

Status:
Complete
Approver:
ruhe
Priority:
Undefined
Drafter:
Steve McLellan
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Kirill Zaitsev

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.