Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When checking if a source is pinned, allow for Mercurial/Bitbucket #517

Merged
merged 1 commit into from Nov 10, 2019
Merged

When checking if a source is pinned, allow for Mercurial/Bitbucket #517

merged 1 commit into from Nov 10, 2019

Conversation

alexwlchan
Copy link
Contributor

Bitbucket repos can be Git or Mercurial (for now, at least!), and Terraform can use either of them as a source. If you were using a Mercurial Bitbucket repo as your module source, it would be reported as unpinned – even if you were pinning to a non-default Mercurial revision.


Spotted while working on #513.

Copy link
Member

@wata727 wata727 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

rules/terraformrules/terraform_module_pinned_source.go Outdated Show resolved Hide resolved
Bitbucket repos can be Git or Mercurial (for now, at least!), and
Terraform can use either of them as a source.  If you were using a
Mercurial Bitbucket repo as your module source, it would be reported as
unpinned -- even if you were pinning to a non-default Mercurial revision.
@wata727 wata727 merged commit 6b60c4c into terraform-linters:master Nov 10, 2019
@wata727
Copy link
Member

wata727 commented Nov 10, 2019

👍

@alexwlchan alexwlchan deleted the bitbucket-allow-mercurial-revision branch November 10, 2019 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants