-
Notifications
You must be signed in to change notification settings - Fork 21
Fix: manage v3 secret from docker entrypoint #1271
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
base: develop
Are you sure you want to change the base?
Fix: manage v3 secret from docker entrypoint #1271
Conversation
83b7a51
to
c4c8a89
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this approach indeed looks easier, but I'm wondering what would be the consequence if they run it with the previously generated secrets? is there any option to smooth it out?
From SC4SNMP 1.15.0, this process has been simplified and can manage all SNMPv3 secrets using a single secrets.json file. | ||
|
||
#### 1. For setups not yet migrated to latest version | ||
First, delete all existing secrets from docker-compose.yaml using manage_secrets.py with the following flags: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will it fail if the user won't do it? I'm afraid nobody's reading the documentation 😂
| `--path_to_compose` | Absolute path to directory with docker compose files | | ||
| `--delete` | Set this flag to true to delete the secret | | ||
|
||
This will delete the secret with a given name from all docker compose files. If this secret hasn't been deleted from `.env` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there an option to delete all?
--contextEngineId 090807060504037 | ||
``` | ||
To create a new secret, | ||
create secrets.json file inside folder (at SECRET_FOLDER_PATH), add entry for the new secrets with all the details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add `` to secrets.json
Description
Handled the creation and deletion of secrets from docker entrypoint using json file, instead of executing manage_secrets.py for each secrets before installation.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Tested locally
Checklist