What is a best practice when integrating Git repositories with Morpheus?

Question

Options

• AAvoiding repository synchronization
• BStoring API keys in plaintext files
• CUsing version control to track changes in automation scripts
• DDisabling webhooks for security reasons

• A
  5% (3)
• B
  4% (2)
• C
  89% (51)
• D
  2% (1)

Explanation

Using version control to track changes in automation scripts (C) is a foundational best practice because it provides a complete audit trail, enables rollback to previous states, and facilitates collaboration - all critical when managing automation workflows in Morpheus.

Why the distractors fail:

• A - Repository synchronization is a core feature of Git integration; avoiding it defeats the entire purpose of connecting Morpheus to a Git repo.
• B - Storing API keys in plaintext is a serious security vulnerability; secrets should use Morpheus Cypher or environment-level credential stores.
• D - Webhooks enable automated synchronization (e.g., triggering Morpheus to pull updates on push); disabling them removes a key automation benefit.

Memory tip: Think of the acronym VCS = Visibility, Control, Safety - version control gives you visibility into what changed, control over what gets deployed, and safety through rollback. Any answer that undermines these (no sync, plaintext secrets, no webhooks) is wrong.

No community discussion yet for this question.