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

Write the repository into secret, test air-gap mode. #382

Merged
merged 1 commit into from
Oct 11, 2022

Conversation

vaikas
Copy link
Contributor

@vaikas vaikas commented Sep 24, 2022

Signed-off-by: Ville Aikas vaikas@chainguard.dev

Summary

TUF server now writes the compressed repo to a secret along with 1.root.json. This way we can test things like air-gap modes, especially in policy-controller without env variables.
Add a test simulating air-gap mode where we bring in a filesystem based TUF repository.

Was tested with:
https://github.com/sigstore/cosign/compare/main...vaikas:cosign:air-gap?expand=1

But I uncommented it for now so we can get this in and then I can add cosign e2e tests there as well once
we cut a release here.

Release Note

  • TUF root writes gzipped tar of the TUF repository, suitable for testing air-gap modes.

Documentation

@vaikas vaikas force-pushed the air-gap branch 3 times, most recently from 3a5b55e to 24e3f49 Compare September 25, 2022 01:23
@vaikas vaikas changed the title WIP: Write the repository into secret, test air-gap mode. Write the repository into secret, test air-gap mode. Oct 1, 2022
Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
@@ -203,6 +205,30 @@ jobs:
run: |
cosign verify --rekor-url ${{ env.REKOR_URL }} --allow-insecure-registry ${{ env.demoimage }}

# Test with cosign in 'airgapped mode'
# Uncomment these once modified cosign goes in.
Copy link
Contributor

Choose a reason for hiding this comment

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

do we have a commit or version we should look for?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll grab the version after it gets committed. I tested with my own fork for functionality, but will need to update the instructions, documentation, so will do after it's been released. Is that ok?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry, I'll grab the 'release' once it gets released with my commit there.

@vaikas vaikas merged commit 5c28667 into sigstore:main Oct 11, 2022
@vaikas vaikas deleted the air-gap branch October 13, 2022 19:33
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