config.functionEnabled
field in your PulsarCluster specification to true
if you are using snctl
or config.function_enabled
field in your PulsarCluster specification to true
if you are using Terraform.
Please note that if you disable Pulsar Functions, you will not able to create new functions in the cluster. Existing functions will continue to run and process messages until they are deleted, but they are not be managed or monitored anymore.
config.transactionEnabled
field in your PulsarCluster specification to true
if you are using snctl
or config.transaction_enabled
field in your PulsarCluster specification to true
if you are using Terraform.
Please note that if you disable Pulsar Transactions on your cluster where you have enabled it before, you are not recommended to disable it because you will disrupt the existing applications that are using transactions and corrupt the data.
config.auditLog
field in your PulsarCluster specification. The audit log configuration allows you to specify which categories of events you want to log.
Here’s how you can configure audit logging:
snctl
:
categories
field is a list of strings that specify which types of events you want to include in the audit log. See the Audit Log Overview for more details on the available categories.
You can add or remove categories based on your specific auditing needs. The exact list of available categories may depend on your StreamNative Cloud version, so consult the documentation for a complete list of supported categories.
Note that enabling extensive audit logging may have performance implications and increase storage requirements. It’s recommended to carefully consider which categories are necessary for your use case and compliance requirements.
To disable audit logging, you can remove the config.auditLog
field in your PulsarCluster specification.