-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Update media
service v4.0 clean up
#27195
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @magodo - I just left one comment about the use of the FourPointOh flag, but otherwise this is looking good. Thanks!
@@ -67,7 +67,10 @@ func (r Registration) DataSources() []sdk.DataSource { | |||
} | |||
|
|||
func (r Registration) Resources() []sdk.Resource { | |||
return []sdk.Resource{ | |||
AccountFilterResource{}, | |||
if !features.FourPointOhBeta() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now that 4.0 has been released we can remove this completely without using the flag
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've checked some other resources and noticed they were still behind the flag (e.g. iottimeseriesinsights). I'd like to follow the current behavior, and expect a commit later to do a bulk delete. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't add 4.0 flags in now that 4.0 has been released. In this case we should probably leave this as it was given that the deprecated resource hasn't bene removed or add the 5.0 flag
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then do you want me to delete the same if
check for the SupportedResources()
? I'm afraid if all of them are deleted, then when the person who is gonna clean up those resources by inspecting the 4.0 flag will miss those resources.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the other if
statement should be fine to remain because it was put in place before the 4.0 release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@catriona-m Done
return []sdk.Resource{ | ||
AccountFilterResource{}, | ||
} | ||
return []sdk.Resource{} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry for the confusion @magodo , I think we need to leave this as it is for now and not remove it, since it wasn't feature flagged before 4.0 was released
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@catriona-m Oh.. I see. That makes sense now. I've reverted it back.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for not noticing this on the previous review, but could you rebase this on main and run make
again? The issue labeller script has been updated to not include labels without regexes in labeler-issue-triage.yml
since this pr was opened. Thanks!
@catriona-m Sure, I've reverted the labeler yaml back now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @magodo LGTM!
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Community Note
Description
#27096 has cleaned up the documents for the 4.0 breaking changes. In particular, it removes the deprecated resources' documents. While the
media
service is missed to do so.Additionally, this PR enclose the
AccountFilterResource
to make it removed in v4.0.PR Checklist
For example: “
resource_name_here
- description of change e.g. adding propertynew_property_name_here
”Changes to existing Resource / Data Source
Testing
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_resource
- support for thething1
property [GH-00000]This is a (please select all that apply):
Related Issue(s)
Fixes #0000
Note
If this PR changes meaningfully during the course of review please update the title and description as required.