Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devel:documentation:modules_reports [2020/03/11 11:50] doischert [Developing and releasing] |
devel:documentation:modules_reports [2021/06/10 11:30] 127.0.0.1 external edit |
||
---|---|---|---|
Line 16: | Line 16: | ||
This report allows you to export the list of identities together with their assigned roles. [[devel: | This report allows you to export the list of identities together with their assigned roles. [[devel: | ||
+ | |||
+ | ==== Identities, their roles and contract ==== | ||
+ | |||
+ | This report is similar to the one above but contains more information. The generated XLSX file has a clear separation between attributes of identity, contract, and role. [[devel: | ||
==== Roles and their identities ==== | ==== Roles and their identities ==== | ||
Line 25: | Line 29: | ||
This report allows you to export the list of identities (with information about their contracts, incl. one contract EAV) together with their assigned roles (and values of role attributes). [[devel: | This report allows you to export the list of identities (with information about their contracts, incl. one contract EAV) together with their assigned roles (and values of role attributes). [[devel: | ||
- | ===== Developing | + | ==== Identities |
- | How to develop a new feature | + | |
+ | This report allows you to export all changes | ||
+ | |||
+ | ==== Identities and their password changes on a system ==== | ||
- | - Create a specification page in private section and consult it with module owner and other colleagues (on Slack). Specification page should contain: | + | This report allows you to export all password changes |
- | - Use-cases - which data should the report contain, what problem does it solve, which client needs it? | + | |
- | - Functional specification - how should it work, edge cases | + | |
- | - Ask a module owner, if this feature can be a part of the module and in which version it will be published | + | |
- | - Create ticket in product Redmine with final requirements and with correct target version | + | |
- | - Implement the feature in a separate GIT branch | + | |
- | - Create merge request to develop | + | |
- | - Get someone from the product team, or the module owner to review your changes | + | |
- | - After successful review, ask module owner to merge you code | + | |
- | Rules for code review: | + | ==== Identities and their system account |
- | * There are [[tutorial: | + | |
- | * All features are documented - the report is mentioned above and has a dedicated page describing its use and configuration | + | |
- | * Changelog is updated | + | |
- | <note important> | + | This report allows you to export all account changes in end systems of the type CREATE, DELETE and ENABLE. You can filter by system, time period, type of operation, |
- | * When developing, use our standard gitflow: | + | ==== Virtual system archived |
- | * Branch per feature. Branch naming as usual. | + | |
- | * Develop on top of the '' | + | |
- | * Master branch contains tagged releases. | + | |
- | * The **only** way for code to get into master is by pull request | + | |
- | * Release process | + | This report allows you to export |
- | - After merging | + | |
- | - Developer creates pull request | + | |
- | - Repo admin (or any other authorized user) reviews the pull request, | + | |
- | - If the pull request is OK, repo admin merges it. | + | |
- | - Repo admin creates a new release in GitHub interface, version is set to '' | + | |
- | - After release, repo admin makes changes on the '' | + | |
====== Read more ====== | ====== Read more ====== | ||
Line 64: | Line 50: | ||
* [[tutorial: | * [[tutorial: | ||
===== Devel guide ===== | ===== Devel guide ===== | ||
+ | * [[devel: | ||
* [[devel: | * [[devel: | ||
* [[devel: | * [[devel: | ||
===== Devel tutorials ===== | ===== Devel tutorials ===== | ||
* [[ tutorial: | * [[ tutorial: |