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

correct handling of deps runtimes #109

Merged
merged 9 commits into from
Nov 28, 2022
Merged

Conversation

apesternikov
Copy link
Collaborator

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

+use dict {"name": ":image" } or [ ":image" ] for images parameter
+more tests
@apesternikov apesternikov requested a review from a team as a code owner November 26, 2022 21:45
@apesternikov apesternikov force-pushed the ap/push_info_in_inages branch from fcae250 to 4f2ee03 Compare November 28, 2022 14:23
if not native.existing_rule(rule_name + name_suffix):
k8s_container_push(
name = rule_name + name_suffix,
image = image,
image = image_label, # buildifier: disable=uninitialized
Copy link
Member

Choose a reason for hiding this comment

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

Does the warning goes away if we handle the result of the image = images[image_name] statement?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

not really, somehow it reacts to the left side which is not actually a variable

skylib/push.bzl Outdated
mnemonic = "CopyFile",
progress_message = "Copying files",
use_default_shell_env = True,
execution_requirements = {"no-remote": "1", "no-cache": "1"},
Copy link
Member

Choose a reason for hiding this comment

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

Why the no-cache parameter required here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it is not really required but it is more efficient to locally copy file (which may come from the cache) rather than talk to remote cache.

skylib/push.bzl Outdated Show resolved Hide resolved
kzadorozhny
kzadorozhny previously approved these changes Nov 28, 2022
@apesternikov apesternikov merged commit 041ba72 into main Nov 28, 2022
@apesternikov apesternikov deleted the ap/push_info_in_inages branch November 28, 2022 17:57
arturo-skydio pushed a commit to Skydio/rules_gitops that referenced this pull request Oct 5, 2023
* +use images or image pushes in k8s_deploy images parameter
+use dict {"name": ":image" } or [ ":image" ] for images parameter
+more tests

* correct handling of dependency runtimes

* test fixes

* use template to generate expected file

* cleanup

* buildifier

* buildifier nit

* explain execution_requirements rationale

* buildifier

Co-authored-by: Konstantin Zadorozhny <[email protected]>
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.

2 participants