CA-390759: Backport (re-add) PBIS (PowerBroker Identity Service from #99) to release/yangtze #100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR backports #99 to the branch
release/yangtze
to be included in the hotfix for Yangtze (if it is taken from this branch):This PR, on top of release/yangtze is the minimal, safe regression fix of missing PBIS data for hotfixes for 8.2 CU1 https://github.com/xenserver/status-report/tree/release/yangtze
It is a backport of #99 (for master), that can be used as basis for future hotfixes.
This change is implemented as flipping the order of executing commands and of capturing files to run commands (e.g. to sync data to disk) first and then traverse the directory trees and finally capture the synced files.
This would be a very deep change, that resulted in one regression that was later discovered and when we go to work on that hotfix, it may be better to take the code that is already validated (running Python 2.7) in XS8.
In summary:
releases/yangtze
is for a fast and minimal fixup for 8.2.CU1bugtool
for Yangtze where we would probably not like to use a backport of all changes by the main branch (used in XS8 with Python 2.7) instead.Product development is then free to use either branch as base for future releases:
One example where using https://github.com/xenserver-next/status-report/tree/master to use it as a stable base where the planned release of #51 which resulted in an issue that needs #88.