Add boolean config options

[tombruijn]

Add config options that are booleans and should be interpreted as such.

Part of #16
[skip changeset]

[backlog-helper]

✔️ All good!

New issue guide | Backlog management | Rules | Feedback

[unflxw]

If active is false, should we not avoid attempting to start the agent (over at agent.py)? That is what the Node.js integration does (s/agent/extension)

[unflxw]

Should the default config include active=True as well? Otherwise users always have to specify it. Ruby derives it from whether push_api_key is non-empty.

Suggested change

	enable_host_metrics=True,
	active=True,
	enable_host_metrics=True,

[tombruijn]

In Ruby you also need to set it in the YAML file and Ruby code. The Push API key only sets it to true if its set through APPSIGNAL_PUSH_API_KEY. This way people can set it based on the env as well with something like: active=(os.environ.get("foo") == "true")

[unflxw]

But people can do that anyway, right? The default will be overriden with whatever users decide to set... Perhaps the default should be false, then, like in the other integrations. Whatever makes sense. We'll need to amend the config in the test setup, though: https://github.com/appsignal/test-setups/blob/main/python/django4-celery/app/appsignal_config.py#L4

[tombruijn]

I figured I'd implement it the same way as the other integrations. We can always discuss behavior changes (please create an issue), but let's keep it like this for this PR.

[tombruijn]

If active is false, should we not avoid attempting to start the agent (over at agent.py)? That is what the Node.js integration does (s/agent/extension)

I've added another commit with this check for the active option.