-
Notifications
You must be signed in to change notification settings - Fork 739
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
FabricBot: Onboarding to GitOps.ResourceManagement because of FabricBot decommissioning #4758
Conversation
…t as FabricBot replacement Owners of the FabricBot configuration should have received email notification. The same information contained in the email is published internally at: https://aka.ms/gim/fabricbot. Details on the replacement service and the syntax of the new yaml configuration file is available publicly at: https://microsoft.github.io/GitOps/policies/resource-management.html Please review and merge this PR to complete the process of onboarding to the new service.
Thank you for your contribution @microsoft-github-policy-service[bot]! We will review the pull request and get back to you soon. |
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.
Fabric Bot should not be active here.
//cc: @JimSuplizio |
@jsquire - no, FabricBot replacement was only done for azure-sdk, azure-sdk-tools and azure-sdk-for- |
Action RequiredOn August 8, Fabric Bot will be turned off and Issues and PR's in this repository will stop receiving the automations it provides. Merging this PR prior to that date will ensure that the automations you have configured will continue without interruption. Please review and merge this PR as soon as possible. See aka.ms/gim/fabricbot for more information |
Final Notice!Next week, on August 8, Fabric Bot will be turned off and Issues and PR's in this repository will stop receiving the automations it provides. Merge this PR ASAP to ensure that the automations you have configured will continue without interruption. See aka.ms/gim/fabricbot for more information |
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.
per Jim, the changeover in automation for this repository will take some additional time.
You may test this build by running Add the following CLI flags
Or with all autorest --version:https://tinyurl.com/2aynk7jq --use:https://tinyurl.com/2dq5v89e or use the following in your autorest configuration: # For changes to autorest core
version: "https://tinyurl.com/2aynk7jq"
# For changes to modelerfour
use-extension:
"@autorest/modelerfour": "https://tinyurl.com/2dq5v89e" If this build is good for you, give this comment a thumbs up. (👍) And you should run `autorest --reset` again once you're finished testing to remove it. |
Add prIssueManagement.yml to onboard repo to GitOps.ResourceManagement as FabricBot replacement
Owners of the FabricBot configuration should have received email notification. The same information contained in the email is published internally at: https://aka.ms/gim/fabricbot. Details on the replacement service and the syntax of the new yaml configuration file is available publicly at: https://microsoft.github.io/GitOps/policies/resource-management.html
Please review and merge this PR to complete the process of onboarding to the new service.