Closed skunkr closed 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
Is this a BUG REPORT or a FEATURE REQUEST ? (choose one):
FEATURE REQUEST INFO
Environment
Cloud provider:
OS details (
printf "$(uname -srm)\n$(cat /etc/os-release)\n"
):Version of Ansible (
ansible --version
):Version of Jinja (
pip freeze | grep -i jinja
):Version of Shade (
pip freeze | grep -i shade
):The openstack-ansible-contrib version (commit) (
git rev-parse --short HEAD
):Copy of inventory files and custom variables used (please omit your secrets!):
Command used to invoke ansible:
Output of ansible run:
Anything else do we need to know:
FEATURE REQUEST INFO
An introduction paragraph with "[tl;dr]" info.
Problem Description
What problem is being solved by the proposed feature?
What are the use cases for End User vs Deployer?
Also describe the target cloud provider.
Proposed Change
Describe the change you would like to make.
Overview
Is there any way to import an exported project to a different project name ? ie: To clone an existing project under a different name.
Alternatives
Security Impact
Other End User Impact
Performance Impact
Other Deployer Impact
Developer Impact
Documentation Impact
Implementation
Describe your plan for implementation steps and potential assignees/contributors.
Acceptance criteria
Provide a definition of done and acceptance criteria.
Testing
Describe how to test this, including manual steps, if any.
Dependencies
References