Github user johnsca commented on the issue:
https://github.com/apache/bigtop/pull/120
@kwmonroe Yes, the motivation behind this change is still valid but there
is now another, cleaner way to get the same result.
The difference between `00-deploy` and `01-bundle` is that the former is
being used as a pre-deploy step ([line
2](https://github.com/apache/bigtop/pull/120/files#diff-707de698394ac34e432f2dec065a7916R2)
in `tests.yaml`). This lets us override the timeout of the initial deploy and
at the time of this PR's submission was the only way to do so.
juju-solutions/bundletester#50 has since been released, however, so we could
replace `00-deploy` and the `bundle_deploy` option with the
`deployment_timeout` option.
I can update this PR, or close and submit a new one.
Oh, and I also think its worthwhile to rev the charms to the most recent
versions, yes?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
