Update github provider version. #325
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
In addition to updating this provider version I have also run
terraform state replace-provider hashicorp/github integrations/github
in order to move all state to the canonical provider. This also protects from unintentional provider version mismatch.
Without this resources created in the module will implicitly use the hashicorp provider without a version restriction.
|
This has been vexing me for weeks and I finally worked out what was missing and causing the provider to regress. With the latest iteration of this we're finally sticking to one terraform provider for all resources and state has been updated to match. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In addition to updating this provider version I have also run
in order to move all state to the canonical provider. This also protects from unintentional provider version mismatch.
To complete the transition and fully remove the other provider, I'll need to complete a deployment so that no current state or current configuration uses the old provider unintentionally.
I may also need to update data sources manually which may not be covered by the provider-replacement, I can't quite tell.