-
Notifications
You must be signed in to change notification settings - Fork 770
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
Ref data source contains incomplete code #1108
Comments
@kfcampbell just want to make sure I understand something about workflow with this repo -- are tests supposed to run on push? It looks like they're in the CI file, but not actually running. This is the most recent build (as of right now) on main: ...and it looks like the test step finishes in anywhere from 10-15s, with this as the output: If this is intentional that's totally fine, but if it's not I'll open a separate issue for that. |
@youcandanch our testing situation is a little goofy right now. We're running unit tests on push, which are executing quite quickly as you've pointed out. Integration tests are run weekly, although they've been reliably failing for some time and aren't currently bringing much value to the product. Once a few immediate fires are put out (EMU support, Dependabot secrets, authorization fixes) I would love to find some time to put towards our testing strategy to gain more confidence with releases. |
@kfcampbell totally understood, only so many hours in the day. Happy to help where I can! |
Using this in a project now totally smoothly, so gonna close this out as resolved. |
Terraform Version
1.1.8
Affected Data Source
Terraform Configuration Files
Expected Behavior
Should get back ref information on the branch/tag.
Actual Behavior
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
.Important Factoids
It looks like when I introduced this data source in #1084, the last commit on the branch was from an older working version. I'm going to open a PR to fix this, but also going to eye the unit tests from that PR, as I'm a little bit perplexed as to how tests ended up passing.
References
The text was updated successfully, but these errors were encountered: