Currently if one does --dry-run it is just semi dry run. It will print the APIServiceExportRequest, but it will see the consumer cluster with the kubeconfig and namespace. This is done so that one can immediately use the returned request.
This is not a dry run as such, because we basically do more than we say. We should fix this, but for this to work, we will need to store kubeconfig and other related objects locally too, so the user can re-use them in follow-up.
Dry run should split the process into 2:
- Establish the contract but do not do anything on consumer side. This should work even without local cluster available.
- Allows to pick assets from dry-run output and continuing the process (even on different cluster)
Currently if one does --dry-run it is just semi dry run. It will print the
APIServiceExportRequest, but it will see the consumer cluster with the kubeconfig and namespace. This is done so that one can immediately use the returned request.This is not a dry run as such, because we basically do more than we say. We should fix this, but for this to work, we will need to store kubeconfig and other related objects locally too, so the user can re-use them in follow-up.
Dry run should split the process into 2: