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

Fix feed creation for dnceng-stage and staging scenarios #8082

Merged
merged 1 commit into from
Oct 22, 2021

Conversation

mmitche
Copy link
Member

@mmitche mmitche commented Oct 22, 2021

  • Don't call GetFeedVisibilityTag when the feed name is explicitly specified
  • Alter GetFeedVisibilityTag to support non-dnceng
  • Alter the default permissions setup method to specify null permissions for non-dnceng

To double check:

- Don't call GetFeedVisibilityTag when the feed name is explicitly specified
- Alter GetFeedVisibilityTag to support non-dnceng
- Alter the default permissions setup method to specify null permissions for non-dnceng
@@ -55,7 +55,9 @@ public AzureDevOpsArtifactFeed(string name, string organization, string project)
}
break;
default:
throw new NotImplementedException($"Organization '{organization}' contains no feed permissions information.");
// Use the default permissions
Permissions = null;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jonfortescue can you take a look at this bit? My recollection is that you changed some stuff around permissions for dnceng-stage, and I want to make sure this captures the change you had made

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The previous implementation of this had no permissions setup for anything but dnceng, so this effectively goes back to that: https://github.com/dotnet/arcade/pull/7700/files

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, this looks fine to me -- this is exactly how it's supposed to be.

Copy link
Contributor

@michellemcdaniel michellemcdaniel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes. Just want to confirm with Jon that he doesn't expect anything for dnceng-stage to break with this (looking at it, I don't expect it to based on the PR he made to enable dnceng-stage, but I just want to have him take a look).

Copy link
Contributor

@jonfortescue jonfortescue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't look like anything will break to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants