Skip to content

Conversation

@dikhan
Copy link
Owner

@dikhan dikhan commented Jan 22, 2022

What problem does this Pull Request solve?

Please link to the issue number here (issue will be closed when PR is merged): Closes #321

Type of change

What type of change does your code introduce to the provider? Please put an x (w/o heading/trailing white spaces) in the boxes that apply:

  • New feature (change that adds new functionality)
  • Bug-fix (change that fixes current functionality)
  • Tech debt (enhances the current functionality)
  • New release (pumps the version)

Checklist

Please put an x (w/o heading/trailing white spaces) in the boxes that apply:

  • I have read and followed the CONTRIBUTING guidelines
  • I have added tests that prove my fix is effective or that my feature works
  • I have made sure code compiles correctly and all tests are passing by running make test-all
  • I have added/updated necessary documentation (if appropriate)
  • I have added the following info to the title of the PR (pick the appropriate option for the type of change). This is important because the release notes will include this information.
    • Feature Request: PRs related to feature requests should have in the title [FeatureRequest: Issue #X] <PR Title>
    • Bug Fixes: PRs related to bug fixes should have in the title [BugFix: Issue #X] <PR Title>
    • Tech Debt: PRs related to technical debt should have in the title [TechDebt: Issue #X] <PR Title>
    • New Release: PRs related to a new release should have in the title [NewRelease] vX.Y.Z

Checklist for Admins

  • Label is populated
  • PR is assigned to the corresponding project
  • PR has at least 1 reviewer and 1 assignee

- Install gorelease via go install as opposed to via the curl command which is no longer supported
@dikhan dikhan self-assigned this Jan 22, 2022
@dikhan dikhan force-pushed the feature/upgrade-go-1.16 branch from 1bbfc05 to 67e17da Compare January 22, 2022 04:26
@dikhan dikhan force-pushed the feature/upgrade-go-1.16 branch from e5e565a to ae03d87 Compare January 22, 2022 04:36
- This test really needs to run against a local test server where we don't rely
on any external endpoint (which is bad) but fixing it for now with the regex
until a proper fix is added.
@codecov
Copy link

codecov bot commented Jan 22, 2022

Codecov Report

Merging #322 (9933a32) into master (82f4472) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #322   +/-   ##
=======================================
  Coverage   93.56%   93.56%           
=======================================
  Files          60       60           
  Lines        3591     3591           
=======================================
  Hits         3360     3360           
  Misses        163      163           
  Partials       68       68           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 82f4472...9933a32. Read the comment docs.

@dikhan dikhan merged commit 594a891 into master Jan 22, 2022
@dikhan dikhan deleted the feature/upgrade-go-1.16 branch January 22, 2022 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade to go 1.16 so Terraform SDK 2.10.1 can be integrated in the plugin

2 participants