New resource to manage MyJFrog / Settings / Cloud Log Streaming

[julien-carsique-sonarsource]

Is your feature request related to a problem? Please describe.
We started using the JFrog Cloud Log Streaming in MyJFrog portal to forward logs to DataDog, but there is no Terraform resource to manage these settings.
We are making heavy use of configuration as code, so all the MyJFrog settings should ideally be available as Terraform resources.
I'm providing more arguments in favor of code vs UI in the last section.

Describe the solution you'd like
A new Terraform resource myjfrog_log_streaming with inputs for configuring the Cloud Log Streaming. Eventually, a set of resources or modules for the various implementations. The one we are interested in is Datadog.

Describe alternatives you've considered
For now, we're doing it by hand on the UI.

Additional context

Could you clarify the purpose of automating this setting? Typically, we automate tasks that need to be performed frequently, but this operation only needs to be done once. Once enabled, it should function without further intervention, so automating it seems unnecessary.

It is not only about automating but also about managing infrastructure and configurations as code (IaC, CasC), which aligns with best practices and brings benefits beyond automation itself.

Our goal is to manage everything by code to reduce the operational burden on our team and avoid reliance on a manual UI-based setup. This approach makes us faster, more efficient, more reliable, and more transparent in managing our infrastructure and services, it allows for better governance and security.

Key benefits of managing this setting via Terraform instead of the UI:

• Automation & Repeatability: Even if this is a one-time setup, defining it as code ensures that it can be reapplied or modified consistently, without manual steps.
• Consistency & Standardization: Using Terraform enforces standardized, predictable and uniform configurations, reducing human errors.
• Change Management & Governance: Infrastructure as Code enables change requests, peer reviews, approval workflows, and structured change management before applying modifications, improving security and compliance.
• Audit & Traceability: Every change is versioned, providing a clear history of modifications, which improves compliance and troubleshooting.
• Security & Access Control: Automating deployments via the API eliminates reliance on specific individuals and working environments, and reduces manual intervention risks. It also enables least privilege access, ensuring that only CI/CD pipelines have modification rights, rather than individual users.
• Scalability & Maintainability: MyJFrog is one of many services we manage. The more we can standardize and manage our configurations as code, the more we improve scalability, reliability, and operational efficiency across our team stacks.

Note that we already faced issues with this single parameter. The feature was activated, configured for a given account. Then it was configured for another account. Then it has been rolled back to the first setup.

• unexpected change by two different teams (miscommunication)
• unexpected limitation in the configuration (documentation and change review)
• lack of history and audit, unknown previous values, unknown actors

By providing Terraform support for this setting, JFrog would empower teams like ours to operate the platform in a more scalable, secure, and controlled way, aligned with modern DevOps practices.

Would you consider adding this to the roadmap?

[alexhung]

@julien-carsique-sonarsource Thank you for the suggestion. I've added this to our plan. cc @mritunjaykumar