You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our codebase relied on data github_repository failing when a repo was not found. It is a good way to ensure during plan that a user has not mispelt a repository name.
PR 1031 introduced a change that resulted in just a message being returned if a repo is missing and the plan continuing. This has resulted in our check being effectively bypassed and deployments breaking.
As this is a minor release, could it be fixed that there is an optional flag to continue on missing repos with the default being to error?
The text was updated successfully, but these errors were encountered:
david-bain
changed the title
PR 1031 introduced breaking changes
PR 1031 (V4.20.1) introduced breaking changes
Jun 16, 2022
Our codebase relied on data github_repository failing when a repo was not found. It is a good way to ensure during plan that a user has not mispelt a repository name.
PR 1031 introduced a change that resulted in just a message being returned if a repo is missing and the plan continuing. This has resulted in our check being effectively bypassed and deployments breaking.
As this is a minor release, could it be fixed that there is an optional flag to continue on missing repos with the default being to error?
The text was updated successfully, but these errors were encountered: