Merge pull request #2212 from OctopusDeploy/zentron-patch-1

Update config-as-code-reference.md

dictionary-octopus.txt

@@ -181,6 +181,7 @@ shiki
 SIEM
 signingkeys
 skiplinks
+snapshotting
 sourcedata
 speculationrules
 srcset

src/pages/docs/projects/version-control/config-as-code-reference.md

@@ -318,6 +318,7 @@ When designing the config-as-code feature, we made several decisions to keep an
 - The Octopus Terraform Provider and OCL are not a 1:1 match. You cannot copy resources between the two and expect everything to work. We want to narrow the gap as much as possible, but as of right now, a gap exists.
 - Octopus currently only supports connecting to git repositories over HTTPS and not SSH. 
 - Shared resources (environments, external feeds, channels, etc.) are referenced by their slug from OCL. The API however will still use IDs.
+- Shared resources referenced in OCL that no longer exist in Octopus Server will result in an error when loading through the portal or API. The provided error message should provide information indicating what reference is no longer valid and should be updated or removed before being loaded again.
 - Shared resources must exist before loading an OCL file into Octopus Deploy. What that means is if you copy the OCL files from one git repo to another, and point a new project at those files, then any shared resource must exist before creating that project. That only applies when projects are in different spaces or on different instances. If the resources do not exist, an error message will appear.
 - Pointing multiple projects to the same folder in the same git repo is unsupported. Please see our [unsupported config as code scenarios](/docs/projects/version-control/unsupported-config-as-code-scenarios) for more information.
 - Converting a project to be version-controlled is a one-way process. At this time, you cannot convert back.