Pavlo Shchelokovskyy d695602397 Add special user options for domain user
those are automated users that are created by Heat and the should
not be subject to restrictions possibly configured in Keystone
for security compliance, as those may break automated nature of things.

Create domain users with several available user options that will
make Keystone ignore:
- password expiry
- requirement to change the password on first use
- lockout after failed auth attempts

There are more things that must be done to properly secure those users
from becoming non-working, but this will be proposed in the followup
patches.

Story: 2005210
Task: 29988

Change-Id: I3152ddb82426cf66f2bd8ed69f53c77c653142bf
2019-05-02 16:12:56 -06:00
2018-01-28 09:11:17 +05:30
2019-04-22 09:36:50 +05:30
2019-04-22 09:36:50 +05:30
2019-04-22 09:36:50 +05:30
2019-04-22 09:36:50 +05:30
2018-02-01 15:38:25 +00:00
2019-04-19 19:33:28 +00:00
2017-12-15 12:39:37 +05:30
2019-04-19 19:33:28 +00:00
2012-03-14 09:25:54 +11:00
2018-07-27 13:38:27 +00:00
2018-01-28 09:11:18 +05:30
2019-04-22 09:36:50 +05:30
2017-03-02 17:42:22 +00:00
2019-04-24 08:52:03 +05:30
2016-01-17 05:20:40 +00:00

Team and repository tags

image

Heat

Heat is a service to orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API.

Why heat? It makes the clouds rise and keeps them there.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://opendev.org/openstack/heat

Python client

Report a Story (a bug/blueprint)

If you'd like to report a Story (we used to call a bug/blueprint), you can report it under Report a story in Heat's StoryBoard. If you must report the story under other sub-project of heat, you can find them all in Heat StoryBoard Group. if you encounter any issue.

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 212 MiB
Languages
Python 99.5%
Shell 0.5%