Skip to content
This repository was archived by the owner on Oct 10, 2020. It is now read-only.

Atomic/util.py: Use tls-verify on skopeo subcommands#1072

Closed
baude wants to merge 1 commit intoprojectatomic:masterfrom
baude:tls_verify_skopeo
Closed

Atomic/util.py: Use tls-verify on skopeo subcommands#1072
baude wants to merge 1 commit intoprojectatomic:masterfrom
baude:tls_verify_skopeo

Conversation

@baude
Copy link
Member

@baude baude commented Aug 17, 2017

Description

In order to avoid warnings from skopeo, we should be using
tls-verify on the skopeo subcommand (like copy) rather than
skopeo itself.

This was reported in issue #1067.

Related Issue Numbers

Pull Request Checklist:

If your Pull request contains new features or functions, tests are required. If the PR is a bug fix and no tests exist, please consider adding some to prevent regressions.

  • Unittests
  • Integration Tests

Atomic/util.py Outdated
args=[]

cmd = [SKOPEO_PATH, 'tls-verify=false', 'delete'] + args + [image]
cmd = [SKOPEO_PATH, 'delete', 'tls-verify=false'], + args + [image]
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this be --tls-verify?

Copy link
Member Author

Choose a reason for hiding this comment

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

yup, good catch

@baude baude force-pushed the tls_verify_skopeo branch from 7a08896 to 50adf2d Compare August 17, 2017 14:20
In order to avoid warnings from skopeo, we should be using
tls-verify on the skopeo subcommand (like copy) rather than
skopeo itself.

This was reported in issue projectatomic#1067.
@baude baude force-pushed the tls_verify_skopeo branch from 50adf2d to 0aad9de Compare August 17, 2017 14:28
@rhatdan
Copy link
Member

rhatdan commented Aug 17, 2017

@rh-atomic-bot r+ 0aad9de

@rh-atomic-bot
Copy link

⌛ Testing commit 0aad9de with merge ae33780...

rh-atomic-bot pushed a commit that referenced this pull request Aug 17, 2017
In order to avoid warnings from skopeo, we should be using
tls-verify on the skopeo subcommand (like copy) rather than
skopeo itself.

This was reported in issue #1067.

Closes: #1072
Approved by: rhatdan
@rh-atomic-bot
Copy link

💔 Test failed - status-redhatci

@rhatdan
Copy link
Member

rhatdan commented Aug 17, 2017

@baude Tests failed?

@baude
Copy link
Member Author

baude commented Aug 17, 2017

@rh-atomic-bot retry

@rh-atomic-bot
Copy link

⌛ Testing commit 0aad9de with merge 69b5d60...

@rh-atomic-bot
Copy link

☀️ Test successful - status-redhatci
Approved by: rhatdan
Pushing 69b5d60 to master...

eyusupov pushed a commit to eyusupov/atomic that referenced this pull request Mar 10, 2018
In order to avoid warnings from skopeo, we should be using
tls-verify on the skopeo subcommand (like copy) rather than
skopeo itself.

This was reported in issue projectatomic#1067.

Closes: projectatomic#1072
Approved by: rhatdan
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants