cloudbreak
cloudbreak copied to clipboard
CB-17474: Added flow to beginning of DL resize which validates if Atlas is up to date.
Jira: https://jira.cloudera.com/browse/CB-17474
The objective is to use the salt changes from CB-17112 to have an automatic flow step at the beginning of resize, which will verify if Atlas is up to date before continuing with the resize. In the case that Atlas is not up to date, the flow will wait for a specified time until it is up to date or the process times out.
This change consists of:
- Flow changes within the Datalake code which is accompanied by the expected addition to the resize flow chain
- Flow changes in the Cloudbreak core code, which is exposed via a stackv4endpoint method
- New logic in cloudbreak core which generates the salt configuration needed for the Atlas salt changes to run
Please note that I am new to these changes and am making a lot of assumptions, specifically basing all of my changes off the backup/restore changes. So if there is anything incorrect or something that could be better, please let me know and I will make the modification.
Local testing has been successful so I am moving this to a real PR.
please use draft PR instead of "waiting-for-test" label if it is not ready to merge
I apologize @horadla23 that label should have been removed over a week ago. This is ready to be reviewed although an ongoing conversation about this is occurring within the Jira comments. Feel free to look at the comments to better understand the discussion before making a review.