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

[Container Registry] Acr delete artifact #17645

Merged
merged 91 commits into from
Apr 2, 2021

Conversation

seankane-msft
Copy link
Member

No description provided.

Copy link
Member

@swathipil swathipil left a comment

Choose a reason for hiding this comment

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

left some comments about things you probably already know :)

Comment on lines 60 to 67
self.created_on = kwargs.get("created_on", None)
self.digest = kwargs.get("digest", None)
self.last_updated_on = kwargs.get("last_updated_on", None)
self.manifest_properties = kwargs.get("manifest_properties", None)
self.operating_system = kwargs.get("operating_system", None)
self.references = kwargs.get("references", None)
self.size = kwargs.get("size", None)
self.tags = kwargs.get("tags", None)
self.content_permissions = kwargs.get("content_permissions", None)
Copy link
Member

Choose a reason for hiding this comment

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

I believe get already defaults to None if key is not in there, so second arg None is not needed.
(not saying this needs to be changed or anything)

cls=lambda objs: [
RegistryArtifactProperties._from_generated(x) for x in objs # pylint: disable=protected-access
],
)

def list_tags(self, **kwargs):
Copy link
Member

Choose a reason for hiding this comment

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

params are specified in the docstring, but it looks like they should be keyword?

@check-enforcer
Copy link

check-enforcer bot commented Apr 1, 2021

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

@@ -127,7 +127,7 @@ async def list_registry_artifacts(self, **kwargs) -> AsyncItemPaged[RegistryArti
last = kwargs.pop("last", None)
n = kwargs.pop("page_size", None)
orderby = kwargs.pop("order_by", None)
return await self._client.container_registry_repository.get_manifests(
return self._client.container_registry_repository.get_manifests(
Copy link
Contributor

Choose a reason for hiding this comment

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

why is the await gone

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 list methods don't return a coroutine, they return an AsyncItemPaged

Copy link
Contributor

Choose a reason for hiding this comment

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

oh yeah lmao, ignore me

Copy link
Member

Choose a reason for hiding this comment

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

We can remove the "async" before the def list_registry_artifacts too

@@ -19,12 +19,14 @@
from azure.identity import DefaultAzureCredential

from testcase import ContainerRegistryTestClass
from constants import TO_BE_DELETED
Copy link
Contributor

Choose a reason for hiding this comment

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

is this constant somethign you want exposed to users? I'm assuming not (which is how it currently is), but just double checking

Copy link
Member Author

Choose a reason for hiding this comment

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

No it is not, it's just so I have a consistent registry imported. I kept misspelling it and eventually made it a constant.

@seankane-msft seankane-msft changed the title [Do Not Merge][Container Registry] Acr delete artifact [Container Registry] Acr delete artifact Apr 2, 2021
@@ -127,7 +127,7 @@ async def list_registry_artifacts(self, **kwargs) -> AsyncItemPaged[RegistryArti
last = kwargs.pop("last", None)
n = kwargs.pop("page_size", None)
orderby = kwargs.pop("order_by", None)
return await self._client.container_registry_repository.get_manifests(
return self._client.container_registry_repository.get_manifests(
Copy link
Member

Choose a reason for hiding this comment

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

We can remove the "async" before the def list_registry_artifacts too

@seankane-msft seankane-msft merged commit 5c4d08b into Azure:master Apr 2, 2021
@seankane-msft seankane-msft deleted the acr-delete-artifact branch April 2, 2021 17:28
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.

4 participants