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

[TechDebt: Issue #317] Deprecate multiregion resource name level #316

Merged
merged 2 commits into from
Nov 2, 2021

Conversation

dikhan
Copy link
Owner

@dikhan dikhan commented Oct 29, 2021

What problem does this Pull Request solve?

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

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

@dikhan dikhan self-assigned this Oct 29, 2021
@dikhan dikhan added this to Backlog in API Terraform Provider (OpenAPI 2.0) via automation Oct 29, 2021
This feature was introduced in early days of the provider to support multi-region. However,
this model was not compatible with Terraform modules since the region was attached to the resource name.
Later, multiregion support was added on the provider level as expected by Terraform enabling
the provider to be used in modules and enabling users to specify the regions on the provider level.

The multi-region support on the resource name level has been still supported till now but it's time
to say goodbye to features that had some value in the past but now don't make sense and makes the code
more difficult to read and maintain.
@dikhan dikhan changed the title Deprecate multiregion resource name level [TechDebt: Issue #X] Deprecate multiregion resource name level Oct 29, 2021
@codecov
Copy link

codecov bot commented Oct 29, 2021

Codecov Report

Merging #316 (96b04d3) into master (1e6a832) will increase coverage by 0.22%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #316      +/-   ##
==========================================
+ Coverage   93.34%   93.56%   +0.22%     
==========================================
  Files          60       60              
  Lines        3651     3591      -60     
==========================================
- Hits         3408     3360      -48     
+ Misses        170      163       -7     
+ Partials       73       68       -5     
Impacted Files Coverage Δ
openapi/openapi_v2_spec_analyser.go 100.00% <ø> (+3.89%) ⬆️
openapi/openapi_v2_resource.go 93.52% <100.00%> (-0.20%) ⬇️

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 1e6a832...96b04d3. Read the comment docs.

@dikhan dikhan changed the title [TechDebt: Issue #X] Deprecate multiregion resource name level [TechDebt: Issue #317] Deprecate multiregion resource name level Oct 29, 2021
@dikhan dikhan marked this pull request as ready for review October 29, 2021 04:59
@dikhan dikhan merged commit 82f4472 into master Nov 2, 2021
API Terraform Provider (OpenAPI 2.0) automation moved this from Backlog to Done Nov 2, 2021
@dikhan dikhan deleted the deprecate-multiregion-resource-name-level branch November 2, 2021 20:01
@dikhan dikhan mentioned this pull request Apr 18, 2022
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Deprecate legacy multi-region support on resource name level
1 participant