-
Notifications
You must be signed in to change notification settings - Fork 52
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
Remove upload to docker registry code snippets #1017
Remove upload to docker registry code snippets #1017
Conversation
✅ Deploy Preview for conda-store ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
316963a
to
982a557
Compare
cda752e
to
0be6b5e
Compare
CONSTRUCTOR_INSTALLER = "CONSTRUCTOR_INSTALLER" | ||
_ = "CONTAINER_REGISTRY" |
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.
Users might have CONTAINER_REGISTRY
as part of their settings (persisted to the database) for build_artifacts_kept_on_deletion
. These are only updated by admins in the admin ui. They are not updated when a new conda_store config is pushed to the server (see ensure_settings function).
If the user has a build artifact type that is not in this list, then the server will error. So, we'll leave this as a valid type.
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.
Good idea.
config=True, | ||
) | ||
|
||
@default("container_registry_image_tag") |
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.
This implementation is not used since the docker build workflows have been disabled
329df3f
to
32e9362
Compare
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.
Minor suggestions. Thanks for this 🚀
CONSTRUCTOR_INSTALLER = "CONSTRUCTOR_INSTALLER" | ||
_ = "CONTAINER_REGISTRY" |
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.
Good idea.
history: List[DockerConfigHistory] = [] | ||
rootfs: DockerConfigRootFS | ||
|
||
|
||
# https://docs.docker.com/registry/spec/api/#errors-2 | ||
class DockerRegistryError(enum.Enum): |
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.
Is it in scope to remove this as well?
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 think we should keep this for now. This is used in the docker registry whenever there are errors. We are deprecating this functionality in pr #1016. But, we'll need to keep it around until the registry is fully removed.
docusaurus-docs/conda-store/references/configuration-options.md
Outdated
Show resolved
Hide resolved
f4bf9ad
to
7b00476
Compare
Follow up to #1001
Description
Following cleaning up removing docker build tasks, this PR removes the functionality for pushing created docker images to container registries and deprecating the related config. This includes:
CONTAINER_REGISTRY
build artifact typeContainerRegistry
implementationContainerRegistry
config settingsPull request checklist