Open PR to update any qhub instances/references in CI/CD (not to be merged until after transferring the repo)

[trallard]

Targets

• https://github.com/Quansight/qhub-integration-test
• https://github.com/Quansight/qhub

open against https://github.com/Quansight/qhub/tree/2022.10.1

[trallard]

Also, the repos from which we deploy Quansight's QHub's instances (which I cannot remember now)

[iameskild]

Mostly completed:

• Update CI to use new nebari cli entrypoint #1480
• https://github.com/Quansight/qhub-integration-test/pull/36

[trallard]

• TODO: Update paths in CI/CD files

[trallard]

Are there any outstanding items here @viniciusdc @iameskild ?

[iameskild]

Just updating the paths in the CI/CD files.

[trallard]

After migration: Update integration tests 🤔

[viniciusdc]

@trallard, I think we can close this once #1498 is merged, right? We can then address IT in another place as that would be internal for a while... and as @aktech commented, we can still use the same paths/pointers to the old repo for some time (though we will move it under the next few days)

[iameskild]

@viniciusdc besides updating the IT README and transferring it to the nebari-dev org, it has been cleaned up. See this PR.

[viniciusdc]

@viniciusdc besides updating the IT README and transferring it to the nebari-dev org, it has been cleaned up. See this PR.

wonderful, did you clear each one of the integration tests repo (providers)? or did they already have the nebari-config.yaml files?

[iameskild]

@viniciusdc besides updating the IT README and transferring it to the nebari-dev org, it has been cleaned up. See this PR.

wonderful, did you clear each one of the integration tests repo (providers)? or did they already have the nebari-config.yaml files?

At the moment, those repos contain both qhub-config.yaml and the new nebari-config.yaml.

[iameskild]

Done 🎉