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

Move CAPABILITIES setting to ISAR instead of in sub-repo #569

Open
tsundvoll opened this issue Jun 6, 2024 · 1 comment
Open

Move CAPABILITIES setting to ISAR instead of in sub-repo #569

tsundvoll opened this issue Jun 6, 2024 · 1 comment
Labels
improvement Improvement to existing functionality stale This issue or pull request already exists

Comments

@tsundvoll
Copy link
Contributor

Describe the improvement you would like to see
The sub-repos rarely, if ever, need to check CAPABILITIES settings, this is more for ISAR to use anyways.

If the sub-repos need to check CAPABILITIES they can still get if from isar.settings.settings.CAPABILITIES

How will this change existing functionality?
It enables more easily and understandably overwrite CAPABILITIES by having a ISAR_CAPABILITIES variable in your environment

How will this improvement affect the current Threat Model?
N/A

@tsundvoll tsundvoll added the improvement Improvement to existing functionality label Jun 6, 2024
@aeshub
Copy link
Contributor

aeshub commented Aug 7, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement to existing functionality stale This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants