This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Apply namespace objects before everything else #812
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
samb1729
reviewed
Oct 25, 2017
| return r | ||
| } | ||
|
|
||
| func mockResourceWithIgnorePolicy(kind, namespace, name string) rscIgnorePolicy { |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
02f34d0 to
0052d31
Compare
|
@tamarakaufler delete your branch :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When creating a kubernetes object which lives in a non-default namespace, the namespace must already exist. This set of changes ensures we apply namespace objects before everything else to prevent that class of error.
Fixes #812