# Page Not Found

The URL `devops/index/to-conditional-or-to-skip-thats-the-ansible-question` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [To conditional or to skip, that's the Ansible question](https://blog.egonzalez.org/devsecops/index/to-conditional-or-to-skip-thats-the-ansible-question.md)
- [Gitlab CI template for DefectDojo](https://blog.egonzalez.org/devsecops/index/gitlab-ci-template-for-defectdojo.md)
- [Vault integration with Gitlab CI](https://blog.egonzalez.org/devsecops/index/vault-integration-with-gitlab-ci.md)
- [OpenDaylight in a Docker](https://blog.egonzalez.org/devsecops/index/opendaylight-in-a-docker.md)
- [Zarf - Airgap deployment in kubernetes](https://blog.egonzalez.org/devsecops/index/zarf-airgap-deployment-in-kubernetes.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://blog.egonzalez.org/devsecops/index/to-conditional-or-to-skip-thats-the-ansible-question.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://blog.egonzalez.org/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://blog.egonzalez.org/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/devsecops/index/to-conditional-or-to-skip-thats-the-ansible-question.md`).

You may also use `Accept: text/markdown` header for content negotiation.