Skip to content
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

Option for gmailctl download to "download" a local XML file #323

Open
macintacos opened this issue Apr 18, 2023 · 2 comments
Open

Option for gmailctl download to "download" a local XML file #323

macintacos opened this issue Apr 18, 2023 · 2 comments
Labels
kind/feature New feature or request lifecycle/keep-alive Denotes an issues or PR that should never be considered stale.

Comments

@macintacos
Copy link

Effectively what I'm trying to do is just import an existing XML file and have it converted to gmailctl's config, just like gmailctl download does for the remote filter XML. Unfortunately, I cannot connect gmailctl directly to my Google account at work, so I want to do the manual export/import dance, but I have a ton of filters already set up that I want to start from.

Effectively, I want something like a --file option for gmailctl download, to tell gmailctl where to "download" the filters from, which in this case would be a local file (although I do admit, that sounds a bit weird saying it out loud, "downloading" a local file). Would this be possible?

@mbrt
Copy link
Owner

mbrt commented Apr 20, 2023

What you're saying makes sense. I would call this import as I think download --file sounds weird.

The issue here is that the way we download filters from Gmail is through the API, which doesn't use the XML format. We only have an exporter to XML, so this would need to be implemented.

I don't think this is very hard, but it takes a bit of time and testing. Potential contributions here are welcome :)

@mbrt mbrt added the kind/feature New feature or request label Apr 20, 2023
@github-actions
Copy link
Contributor

This issue is stale because it has been open for 30 days without activity.
This will be closed in 7 days, unless you add the 'lifecycle/keep-alive' label or comment.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity, has become stale and will be auto-closed. label May 21, 2023
@mbrt mbrt added lifecycle/keep-alive Denotes an issues or PR that should never be considered stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity, has become stale and will be auto-closed. labels May 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request lifecycle/keep-alive Denotes an issues or PR that should never be considered stale.
Projects
None yet
Development

No branches or pull requests

2 participants