Exporting scenarios to other datacenters #6148
Unanswered
FrankAllanRJ
asked this question in
Spoke Questions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey guys.
Is there any planning to perform export/import of entire spoke projects or scenarios, taking all the files together, to be imported in full into another environment?
Explaining better:
I have an environment where I create all the metaverses I need. But eventually, I need to reproduce one or more scenarios in a customer's environment, which is under another AWS AccountID.
Today, if I use the export in .spoke format and import it into the client's environment, all URLs of external objects are pointed to our environment, causing the cost of consumption by the client's users to fall on our account, instead of the environment of the client, which is not desirable.
If I export in binary format, in addition to the same thing happening in terms of data consumption, it is not possible to edit to redirect the URLs.
Ideally, an export type should be added to Spoke that generates a "package" (zip, tar.gz, for example) containing all the files necessary for creating the scenario. And when we were to import this "package" into another environment (another AWS Account ID or any datacenter), the import process would already be in charge of uploading the files to the right places in the filesystem and S3 and would also update the Database.
Would it be possible?
Are there any plans for that?
Best regards.
Beta Was this translation helpful? Give feedback.
All reactions