You are correct in my issue. The environment file is creating a new resource type and associating the new resource type with a URL to retrieve a file that defines the resource type. Since my template references the new resource type, the template validation is failing.
Do you feel we can cover this same issue with this bug, or should a new bug be created. The root cause is the same so I am thinking a single bug report that documents template validation failures due to the env file not being incorporated into the template validation would suffice.
You are correct in my issue. The environment file is creating a new resource type and associating the new resource type with a URL to retrieve a file that defines the resource type. Since my template references the new resource type, the template validation is failing.
Do you feel we can cover this same issue with this bug, or should a new bug be created. The root cause is the same so I am thinking a single bug report that documents template validation failures due to the env file not being incorporated into the template validation would suffice.