Activities connected to items that exist in a different workspace will always point to the original item unless parameterized in the find_replace section of the parameter.yml file.
Activities connected to items within the same workspace are re-pointed to the new item in the target workspace.
Connections are not source controlled and must be created manually.
The executing identity of the deployment must have access to the connections, or the deployment will fail.
Environments attached to custom spark pools attach to the default starter pool unless parameterized in the spark_pools section of the parameter.yml file.
The find_replace section in the parameter.yml file is not applied to Environments.
Resources are not source controlled and will not be deployed.
Environments with libraries will have high initial publish times (sometimes 20+ minutes).
Reports connected to Semantic Models outside of the same workspace always point to the original Semantic Model unless parameterized in the find_replace section of the parameter.yml file.
Reports connected to Semantic Models within the same workspace are re-pointed to the new item in the target workspace.
Semantic Models connected to sources outside of the same workspace always point to the original item unless parameterized in the find_replace section of the parameter.yml file.
Semantic Models connected to sources within the same workspace may or may not be re-pointed; it is best to test this before taking a dependency. Use the find_replace section of the parameter.yml file as needed.
Initial deployment requires manual configuration of the connection after deployment.