Added information on some complex inputs

[RodrigoCuryZup]

No description provided.

[snykbotzup]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)

[gitbotzup]

PR Summary

This pull request enhances the project documentation by adding a new section to the README.md file. The new section, "More information on some inputs," provides detailed explanations and usage examples for the BRANCH, DYNAMIC_INPUTS, and WORKDIR inputs. These improvements aim to clarify advanced use cases and help users better understand how these inputs influence the deployment process, especially in scenarios involving multi-infrastructure repositories or dynamic plugin input injection.

---

Changed Files

README.md

• Added: A new section titled "More information on some inputs."
• Details:
  • Each input (BRANCH, DYNAMIC_INPUTS, WORKDIR) is described within a collapsible <details> block.
  • Includes usage notes, example directory structures, and sample code snippets (e.g., Jinja template usage for DYNAMIC_INPUTS).
  • The documentation now clarifies the impact of these inputs on deployment behavior, with a focus on advanced and dynamic use cases.

---

Security Advice

Warning

Potential Security Consideration:
While the changes are documentation-only and do not directly affect code execution, the new documentation highlights the ability to inject dynamic inputs into plugins. If not properly validated or controlled, misuse of dynamic inputs could lead to unintended changes in Infrastructure as Code (IaC) deployments.
Reviewers should ensure:

• Dynamic inputs are always validated and sanitized.
• Access to input injection is restricted to trusted users.
• Documentation clearly communicates the risks and best practices for using dynamic inputs.

---

Please review the new documentation for clarity and completeness, and consider the security advice above when using dynamic inputs in your workflows.
This is an AI-generated summary, which may be innacurate.
This aims only to assist human reviewers, and does not replace code reviews in any way.
Use responsibly and please submit any feedback to this form.