Fix app_tel_for_sok app.conf install stanza header

[mmarod]

Description

Fixes #1723

Key Changes

Fixes the first line of the app.conf within app_tel_for_sok so it does not have a -e prefix.

Testing and Verification

Locally built the operator and confirmed that app.conf is correct.

splunk@splunk-ingestor-ingestor-0:/opt/splunk$ cat /opt/splunk/etc/apps/app_tel_for_sok/default/app.conf
[install]
is_configured = 1

[ui]
is_visible = 0
label = Splunk Operator for K8s

[launcher]
author = Splunk
description = When telemetry is enabled, this app is used to help Splunk understand how many customers are deploying Splunk using Splunk Operator for K8s
version = 1.0.0

Related Issues

Jira tickets, GitHub issues, Support tickets...

PR Checklist

• Code changes adhere to the project's coding standards.
• Relevant unit and integration tests are included.
• Documentation has been updated accordingly.
• All tests pass locally.
• The PR description follows the project's guidelines.

[github-actions]

CLA Assistant Lite bot CLA Assistant Lite bot All contributors have signed the COC ✍️ ✅

[Copilot]

Pull request overview

Fixes the invalid app.conf generated for the telemetry app (app_tel_for_sok) by avoiding echo -e, which can be emitted literally as -e on some /bin/sh implementations.

Changes:

• Replace echo -e with printf '%s' when writing default/app.conf and metadata/default.meta for the telemetry app.
• Keep the rest of the telemetry app creation flow unchanged (directory creation + reload/bundle push).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mmarod]

recheck

[vivekr-splunk]

I have read the CLA Document and I hereby sign the CLA

[vivekr-splunk]

I have read the Code of Conduct and I hereby sign the COC

[mmarod]

I have read the Code of Conduct and I hereby sign the COC

[mmarod]

I have read the CLA Document and I hereby sign the CLA

[mmarod]

I have read the Code of Conduct and I hereby accept the Terms

[kubabuczak]

This PR introduced incorrect syntax:

Secrets cannot be directly referenced in if: conditionals. Instead, consider setting secrets as job-level environment variables, then referencing the environment variables to conditionally run steps in the job.

src: https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/use-secrets