cloudback / issue-tracker Goto Github PK

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

I am on a trail
I have two organizations that I need to back up. I have the proper plans for both organizations and successfully backed up the code to CloudBack for the first test. I then added an S3 bucket and changed all of the settings to use the s3 bucket instead.

I know only see the AutoElevate org's repositories, I cannot see the PasswrdBoss repositories anymore.

Current view:

Cloudback settings on Autoelevate:

Cloudback settings on Password Boss:

What am I missing not to be able to see all repositories from both orgs on the same view in Cloudback?

Describe the bug
View all function n cards view and the complete table view is not working for me

To Reproduce*
Steps to reproduce the behavior:

1. Go to 'table view' or click on view all in cards view

Expected behavior
should work

Screenshots

Desktop (please complete the following information):

• OS: macOs
• Browser safari

Additional context
Add any other context about the problem here.

Describe the bug
Whenever I try to back-up my GitHub-Repo I get a "Limit exceeded" error-message

To Reproduce
Steps to reproduce the behavior:

1. Setup a backup for a Github-Repo
2. Trigger the backup
3. Wait for the error-message

Expected behavior
The backup succeeds without an error

Screenshots

Is your feature request related to a problem? Please describe.
I would like to automatically backup all non-archived repositories for an organization. I am looking to onboard all of my companies organization's hundreds of repositories. However, I do not want to backup archived repositories. Currently it appears I would have to manually go through and find and disable the 70 something out of 400 repositories that are archived after selecting "enable all" on initial setup.

Also, once a repository is archived, I no longer what new backups to be taken as there is no reason to have scheduled backups for a read-only repo.

Describe the solution you'd like
Add option to enable backups for all non-archived repositories
Add option to disable backups for repositories that have been archived.

Describe the bug
When pull request comments are restored, they are restored as a single line with the username but no original comment text.

To Reproduce
Steps to reproduce the behavior:

1. Create a PR in a repository
2. Add a comment to the PR
3. Back up the repository on https://app.cloudback.it
4. Delete the repository
5. Restore the repository (and wait for it to fully finish)
6. View PR in restored repository

Expected behavior
The PR had comments in it originally, and I expect that they will be restored when the repository is restored. I know there are API limitations for this, but it seems like there is actually a bug here.

The contents of the PR comments are simply: " wrote at " without any of the original text at all. The pull-requests.json file in the backup has the text of the original comment... it is just not restored.

Screenshots
Before deleting and restoring the repository:

After deleting and restoring the repository:

Desktop (please complete the following information):

• OS: Linux (Ubuntu 20.04)
• Browser Firefox
• Version 124.0.2

Additional context
I did not check if the initial comment was restored correctly. My test PRs had no text in the main PR comment.

Is your feature request related to a problem? Please describe.
I want to use a GCS bucket as my storage location. On setting up my org with hundreds of repositories, there is no way to select another storage option has it hasn't been created yet. After I'm in the main interface, I can then add a new storage option. However, to get this to apply to the hundreds of already enabled repos I'd have to manually edit each one by hand.

Describe the solution you'd like
A way to change the storage location for all enabled repos

I am attempting to download a github repo backup but we are not receiving the email with the password.

I have checked my spam filter and had our corporate IT check as well but we don't know who the email is coming from to be able to whitelist - is it cloudback.it? github?

Can you please confirm that the email will be going to [email protected] for our account es99dev?

Thank you

The metadata is saved in JSON inside backups. Currently, the JSON is stored in a compact format, without idents. In order to improve readability, better to format JSON with idents.

Describe the bug
GIT PUSH fails during restore:

 ! [remote rejected] master -> master (refusing to allow a GitHub App to create or update workflow .github/workflows/wf.yml without workflows permission)
error: failed to push some refs to 'https://github.com/cloudback/wf'

Possible solution:

• Extend GitHub Application grants to workflow

Is your feature request related to a problem? Please describe.
It would be nice to add support for openstack swift as well

Describe the solution you'd like
I should be able to backup my github repositories to openstack swift/ s3 compatible storage

Describe alternatives you've considered
NA

Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have no visibility of third party service tools. I don't feel like entering their web interface to check the status of the scheduled jobs.

Describe the solution you'd like
I would like to receive a slack message on my DevOps team channel with the result of the github backup status (successes/failures) so that I can know if my backups are indeed working and quickly work on failed ones.

Describe alternatives you've considered
Log in everyday into the web interface to check status and/or check email notification for failures.

Additional context
Example:

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Add support of Microsoft OneDrive storage as a backup target

• https://onedrive.live.com/

We selected a schedule of daily at 8pm s and yet for all of our repos the schedule says daily at 6am. We even tried to do a bulk operation to update it and it didn't work. Any advice?

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

I selected a backup to download from the portal to test opening it. The first backup I downloaded, I received the password immediately.

Because that was stored on your Storage (my initial backups) - I wanted to test it on my S3 bucket. I downloaded today's from the same repository - but never received the email containing the password. (The one with an X)

I have now attempted to download other repositories as tests in the AutoElevate Respoitorty, and I'm not getting any emails.

The emails are not located in my spam filter.

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
I thought it might be nice if when using S3 storage, when the app performs the PutObject action to place the backup zip file, if the object could be tagged with something like repository=<thing>.

Describe alternatives you've considered
N/A

Additional context
I was chatting with our team this morning and looking at the S3 bucket where our backups are stored and of course all the zip file objects are named with metadata names which I assume are generated within Cloudback. We thought it might be nice to be able to browse to the bucket and at a glance, see which backup is which from a repo perspective in GitHub? Now, of course changing the names of the backup objects I appreciate might be a bit of a larger change within the code base, but adding tags to the objects would at least allow a user to search in the AWS console in S3 and filter by object tag for the name of the GitHub repository which they are looking for the backup for.

The reason we might want to do this, is if the Cloudback console is unavailable for some reason, or if we want to use S3 bucket replication or any other mechanism which might mean we want to check our backup objects at a glance within AWS.