Skip to content
Discussion options

You must be logged in to vote

If the resource hasn't been deployed, then you can ignore the deploy error from the pipeline for that commit, as it will self resolve in the next commit when it tries to deploy other things.

If you have mixed this change with other changes and the error is blocking the roll out of the other resources, then the best course of action is to isolate this particular change into a separate branch so that the pipeline will only act on the relevant changes that need to be deployed.

If on the other hand you want to use this folder structure, in general it is not recommended to nest folders like this because it breaks the operating model of Terragrunt, where it depends on using find_in_parent_folders

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by yorinasub17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
1 participant