-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify download-edit-redeploy workflow #270
Comments
Do the changes described in #268 (see last comment) sound like they'd do what you want? |
I'm not sure it does. FWIW I think we've come to a workaround, at least- documenting that collaboration requires duplicating the |
Are we sure we want to promote this workflow? I think ideally we'd encourage folks to share the code on github or similar? |
Agree that Connect is not a source-control system. There is still a case for simpler "publish to existing content" when you don't have the original |
We may also want to reconsider the logic here: Lines 337 to 339 in 800a9eb
I'm pretty sure we want to always save the deployment record, even if you're updating someone else's content. But we do want to preserve as a much as possible, probably including the previous account name. |
And think about this code, which which looks up an Lines 707 to 714 in 8a8df23
|
Probably makes sense to tackle at the same time as #677 |
Right now, it's possible to download a bundle, edit it, and redeploy it to the same endpoint using the following steps:
Where
1234
is the ID of the downloaded app.Things that make this less than awesome:
app-<appId>-<bundleId>.tar.gz
. There is no cue distinguishing app ID from bundle ID other than position.The text was updated successfully, but these errors were encountered: