Closed charbull closed 2 years ago
Great idea! Would certainly shorten the migration workflow. Really appreciate your review and feedback. The project creation and registry migration are all done via APIs so very doable.
At the moment it is lower priority on our list. Users are still required to interface with the Google Cloud marketplace to activate, IAM to get their service tokens and ClearBlade registration page all require a manual UI step. Additionally, we hope the project creation and initial registry migration is a one time task vs something that must be repeated like device copy. Consequently our current priorities are staying pretty focused on getting all the SDKs completed and providing a complete migration project test and validation plan.
Happy to take additional input on moving it up in prioritization.
Will leave this request open for us to revisit later in the quarter
Hi @aallsbrook, if the number of registries is small. Some users might have around 200+ registries to migrate. Creating those manually is not great :) That said, it is feasible to write a script to --curl-- create the registries, fetch the credentials and call the tool. I don't speak Go otherwise I would have attempted extending it :)
Cheers
Appreciate the additional information. No doubt when we bump into 200+ registries we will work to prioritize and support that user.
@aallsbrook fyi a pull request to have this supported: https://github.com/ClearBlade/clearblade-iot-core-migration/pull/7
The next PR to create regsitries. ideally, the user could rely on the clearblade service account to create those instead of credentials by the registry
Hi,
A very useful feature would be to enable the registry creation and fetching the credentials of the registry/systemKey/cbToken to execute the migration. Currently, users MUST do the following:
A nice feature would be to extend the tool to:
Thoughts?
Cheers.