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

Change the structure of the secret configurations in Vault #54

Closed
5 tasks done
obervinov opened this issue Mar 24, 2024 · 0 comments · Fixed by #37
Closed
5 tasks done

Change the structure of the secret configurations in Vault #54

obervinov opened this issue Mar 24, 2024 · 0 comments · Fixed by #37
Assignees
Labels
enhancement New feature or request

Comments

@obervinov
Copy link
Owner

obervinov commented Mar 24, 2024

Is your feature request related to a problem? Please describe.
Bring the structure of secrets with the configuration of various APIs to the same view and add an additional attribute that disables or enables these apis.

Describe the solution you'd like

  • change the old secrets mega/dropbox -> uploader-api
  • change the old secret instagram -> downloader-apii
  • desired key scheme for uploader-api
    {
      "username": "username",
      "password": "password or token",          
      "storage-type": "mega or dropbox or local",
      "enabled": true or false (for disabled class),
      "exclude-types": "*.txt,*.tmp",
      "source-directory": "tmp/",
      "destination-directory": "mybot/"
    }
  • desired key scheme for downloader-api
    {
      "username": "username",
      "password": "password or token",
      "login-method": "anonymous or password or session"
      "session-file": "path to session file",
      "enabled": true or false (for disabled class),
      "user-agent": "client user agent",
      "fatal-status-codes": [400, 401, 429, 500]
    }
  • then delete all environment variables that depend on the new structure
    - TEMPORARY_DIR
    - STORAGE_TYPE
    - STORAGE_EXCLUDE_TYPE
    - INSTAGRAM_SESSION
    - INSTAGRAM_USERAGENT
    Describe alternatives you've considered
    None

Additional context
None

@obervinov obervinov added the enhancement New feature or request label Mar 24, 2024
@obervinov obervinov added this to the release/v2.1.0 milestone Mar 24, 2024
@obervinov obervinov self-assigned this Mar 24, 2024
obervinov pushed a commit that referenced this issue May 28, 2024
…`rate limits`, `queue` and code refactoring (#37)

## v2.1.0 - 2024-05-28
### What's Changed
**Full Changelog**: v2.0.0...v2.1.0 by @obervinov in #37
#### 🐛 Bug Fixes
* #23
#### 📚 Documentation
* #26
* Update repository issues template
#### 💥 Breaking Changes
* Add `PostgreSQL` support to the bot stack instead of `Vault`. All bot data except `configurations` and `user data` is now stored in the database.
* Remove outdated method for processing full account data per link of `user profile`.
* Move all configuration of components form `environment variables` to the `Vault`.
#### 🚀 Features
* #54
* #32
* #30
* #28
* #14
* #20
* #27
* #24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
1 participant