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

Rehauling Directories, Path Logic, and Test Logic to Conform to Automated Payload (/lib) #247

Merged
merged 3 commits into from
Feb 13, 2024

Conversation

tbarnes94
Copy link
Member

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)
Feature # (details)

Type of change

Please delete options that are not relevant.

  • 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 not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s).

  • TestValidateDeployment_ContainerAllowedImages [x]
  • TestValidateDeployment_ContainerEnforceProbes [x]

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

…l get from rustam's automation. Lot of things renamed to better conform to actual behavior. TestManifests now have an array of paths for success and error cases, so there can be 1 to N success/error cases per constraint/template. Added semantic version sorting for grabbing the latest constraint/templates available.
// methods for retrieval of deployment manifest, constraint templates, and constraints
func (fc FileCrawler) ReadDeployment(path string) (*unstructured.Unstructured, error) {
// sorts the list of supported safeguards versions and returns the last item in the list
func getLatestSafeguardsVersion() string {
Copy link
Member

Choose a reason for hiding this comment

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

Fine for now, but in the future we should allow the user to specify the version

@tbarnes94 tbarnes94 merged commit 4685098 into staging Feb 13, 2024
101 of 104 checks passed
@tbarnes94 tbarnes94 deleted the tbarnes94/directory-rehaul branch February 13, 2024 15:01
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