Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds independent API lifecycle coverage for project access keys, repositories, inventories, and templates. Each scenario checks persisted updates, explicitly deletes its resource, and verifies both HTTP 404 on subsequent reads and absence from the collection.
Separate task scenarios verify that an updated template executes the new playbook with its saved
--checkargument, recent tasks are returned newest first, and onestop_all_tasksrequest stops two simultaneously running executions. The existing access-key security test also checks that original and rotated credentials remain absent from task output.Resource-specific typed fixtures and project/template preconditions keep each test independent. Domain steps expose the additional GET/PUT/DELETE operations; cleanup accepts already-deleted resources while explicit delete assertions still require HTTP 204.
Validation:
core-sqlite-local, using the Semaphore develop image built from232bfb242b1eeda93717098d46283a7582279f0a../gradlew spotlessApply qualityGatepassed.git diff --checkpassed.