Closed jku closed 6 months ago
cc @javanlacerda please have a look:
cc @javanlacerda please have a look:
- did I miss anything?
- does the approach of doing two runs of the test suite in a single GH action call make sense?
Hey @jku! It seems awesome!
I am just wondering if we could have staging as default and production as optional. I mean, It could decrease the production infrastructure usage for development proposes. Does it make sense?
I am just wondering if we could have staging as default and production as optional. I mean, It could decrease the production infrastructure usage for development proposes. Does it make sense?
I think once we're sure this works the default should be to test everything (and not testing with production seems like a decision that could bite a client developer in the behind). Whether there is a use case to ever test only staging I don't know...
Whether there is a use case to ever test only staging I don't know...
I personally can't think of one 🙂 -- IMO we can save ourselves a state here and make staging tests "additive" rather than dealing with different combinations.
This might be enough to close #121.
Summary
Do several small changes required to support staging tests in self-test
enable-staging
action input defaults to false: we may want to reconsider before releasing -- maybe opt-out is better?TODO?
--staging
flag is sort of documented in cli_protocol.md but it could probably be improvedTest run https://github.com/sigstore/sigstore-conformance/actions/runs/8017481217