Skip to content
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.

Introduce a minimal set of conformance tests for rukpak provisioners #272

Open
timflannagan opened this issue Apr 27, 2022 · 3 comments
Open

Introduce a minimal set of conformance tests for rukpak provisioners #272

timflannagan opened this issue Apr 27, 2022 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
backlog

Comments

@timflannagan
Copy link
Contributor

Goal: introduce a minimal set of basic, straight forward conformance tests that can be used to validate rukpak provisioners down the line.
@timflannagan timflannagan added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 27, 2022
@timflannagan timflannagan added this to the backlog milestone Apr 27, 2022
@github-actions
Copy link

github-actions bot commented Sep 7, 2022

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2022
@tylerslaton tylerslaton removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 13, 2022
@tylerslaton
Copy link
Contributor

@timflannagan Would you mind coming back to this issue with some more fleshed-out ideas of what you'd like to see here? That should get this into a more actionable state for contributors.

@github-actions
Copy link

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
backlog
Development

No branches or pull requests
2 participants
@timflannagan @tylerslaton