Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

Configure a custom "default" schema location and policy config for air gapped environments #737

Open
uriahrokach opened this issue Jul 24, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request WIP Working in progress (will be deployed soon)

Comments

@uriahrokach
Copy link

uriahrokach commented Jul 24, 2022

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

We want to use datree in our air - gapped environment, and so far it's working great, but every time we use it we have to specify --schema-location and --policy-config and then specify our own configuration.

We would like to write a configuration of our own, upload it to git, and then configure it as our default policy, so that we don't have to specify every time.

This would also benfit other teams in our company that would like to use datree, for which we can configure our own policy and then distribute our configuration.

Describe the solution you'd like

There are two good possible solutions in my opinion: The first being two environment variables for the DATREE_SCHEMA_LOCATION and DATREE_POLICY_CONFIG. The second can be configuring this using datree config command.

Describe alternatives you've considered

We have have thought of creating an alias or a bash function for the datree command that contains this, but this would be much better "out of the box".

@uriahrokach uriahrokach added the enhancement New feature or request label Jul 24, 2022
@adifayer
Copy link
Contributor

Great idea!
Here are the product requirements for who ever wants to grab this one:

  1. Configure --policy-config and --schema-location values by adding it to the config file using the datree set config command or editing the config yaml file itself.
  2. Order for reading values-
    CLI flag command > Env variable > Config file

@adifayer adifayer added the up for grabs Looking for a contributor to take this task label Jul 24, 2022
@Meyazhagan
Copy link
Contributor

@adifayer I would like to contribute on this enhancement. And I am working on it.

@eyarz eyarz added WIP Working in progress (will be deployed soon) and removed up for grabs Looking for a contributor to take this task labels Apr 11, 2023
@eyarz
Copy link
Member

eyarz commented Apr 11, 2023

@Meyazhagan you got it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request WIP Working in progress (will be deployed soon)
Projects
None yet
Development

No branches or pull requests

4 participants