password generated before deployment if user does not set them via constraints.
Bug #1636987 reported by
Toure Dunnon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Use custom parameter constraint to identify such parameters, allowing the user to add a custom template which can specify that certain parameter that is generated. GUI can use this information too as it is embedded in plan (THT).
| tags: | added: workflows |
| description: | updated |
| summary: |
- password-like parameters are automatically generated before deployment - if user does not set them + password generated before deployment if user does not set them via + constraints. |
| description: | updated |
| tags: | added: tripleo-heat-templates |
| Changed in tripleo: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in tripleo: | |
| status: | Confirmed → Triaged |
| milestone: | none → ocata-2 |
| Changed in tripleo: | |
| milestone: | ocata-2 → ocata-3 |
| Changed in tripleo: | |
| milestone: | ocata-3 → pike-1 |
| Changed in tripleo: | |
| milestone: | pike-1 → pike-2 |
| Changed in tripleo: | |
| assignee: | nobody → Adriano Petrich (apetrich) |
| Changed in tripleo: | |
| milestone: | pike-2 → pike-3 |
| Changed in tripleo: | |
| assignee: | Adriano Petrich (apetrich) → nobody |
Revision history for this message
| Julie Pichon (jpichon) wrote | #1 |
| Changed in tripleo: | |
| milestone: | pike-3 → pike-rc1 |
| Changed in tripleo: | |
| milestone: | pike-rc1 → queens-1 |
Revision history for this message
| Dougal Matthews (d0ugal) wrote | #2 |
| Changed in tripleo: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
I'm a bit confused with the title and short description, this sounds similar to what we already do for passwords at the moment:
https:/
https:/
which get auto-generated and then used only if not set in a template/
Is this about moving this to the templates, so that we don't need to keep a hard-coded list anymore? Or about making the system more generic / customisable by the deployer? Thank you.