Add support to depreman to ingest a configuration object from the environment.
The main use case I envision for this is that a user runs depreman in their CI on a regular schedule for their latest release (with the goal of knowing when a new release is necessary due to a deprecated dependency). But sometimes a deprecated dependency does not warrant a new release, hence you'd want to instruct depreman to ignore it. But in this scenario you can't push a commit with an updated depreman config because then it wouldn't be the release commit anymore. Hence you'd need some alternative way to do this.
For example, with GitHub Actions one could specify the config as a vars variable and provide it to Depreman as an env variable.
Add support to
depremanto ingest a configuration object from the environment.The main use case I envision for this is that a user runs
depremanin their CI on a regular schedule for their latest release (with the goal of knowing when a new release is necessary due to a deprecated dependency). But sometimes a deprecated dependency does not warrant a new release, hence you'd want to instructdepremanto ignore it. But in this scenario you can't push a commit with an updateddepremanconfig because then it wouldn't be the release commit anymore. Hence you'd need some alternative way to do this.For example, with GitHub Actions one could specify the config as a
varsvariable and provide it to Depreman as anenvvariable.